pagarme_update_recipient_default_bank_account

WHAT IT DOES

What pagarme_update_recipient_default_bank_account does on Payments MCP

AI agents use pagarme_update_recipient_default_bank_account to create or update resources in Payments MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Payments MCP environment.

WHY IT NEEDS A POLICY

Why pagarme_update_recipient_default_bank_account needs a policy

Although this tool modifies financial account routing information, it is a reversible update operation rather than an irreversible destruction or an actual movement of funds. The severity is high because updating a recipient's bank account details could redirect payments to an attacker's account if misused, but it remains in the Write category.

From the tool's definition Tool name includes 'update' and description states 'Atualiza a conta bancária padrão' (updates the default bank account), which modifies recipient financial data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pagarme_update_recipient_default_bank_account Rate-limited

pagarme_update_recipient_default_bank_account stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pagarme_update_recipient_default_bank_account": {
      "limits": [
        {
          "counter": "pagarme_update_recipient_default_bank_account_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Payments MCP, so you can run agents against it safely.

FAQ

Questions about pagarme_update_recipient_default_bank_account

What does the pagarme_update_recipient_default_bank_account tool do? +

Atualiza a conta bancária padrão de um recipient (personal) no Pagar.me. It is categorised as a Write tool in the Payments MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pagarme_update_recipient_default_bank_account? +

Register the Payments MCP server in PolicyLayer and add a rule for pagarme_update_recipient_default_bank_account: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Payments MCP. Nothing to install.

What risk level is pagarme_update_recipient_default_bank_account? +

pagarme_update_recipient_default_bank_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pagarme_update_recipient_default_bank_account? +

Yes. Add a rate_limit block to the pagarme_update_recipient_default_bank_account rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block pagarme_update_recipient_default_bank_account completely? +

Set action: deny in the PolicyLayer policy for pagarme_update_recipient_default_bank_account. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides pagarme_update_recipient_default_bank_account? +

pagarme_update_recipient_default_bank_account is provided by the Payments MCP server (lpillonwp/mcp-payments). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.