What an agent can do

Scope of the tools#

Of the 39 tools, 29 only read and 10 change state. 5 of those 10 are marked as sensitive.

The ones marked as sensitive are refunds and captures, charges with stored cards, deleting payment links, deleting contacts and managing subscribers.

One group has no published reference: charges with stored cards. It is active on the server and counts towards these numbers, so a connected agent can use its tools, but the portal does not publish the per-tool detail. Ask support if you need it.

Permission inheritance#

The server uses the merchant API credentials, so it inherits exactly its permissions: it does not impose additional barriers per tool. An active user can issue refunds and run bulk charges.

Controls that do exist#

• A per-user activation switch, which cuts access without deleting the account.
• A separate administrator role, which only serves to manage users and credentials.
• A rate limit of 60 calls per minute per user.

Human confirmation#

The per-tool detail, with parameters and output, lives on each group page and in the mcp.json.