pagarme_create_recipient · Payments MCP: Risk & Policy

WHAT IT DOES

What pagarme_create_recipient does on Payments MCP

AI agents use pagarme_create_recipient to commit financial operations through Payments MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why pagarme_create_recipient needs a policy

This tool creates a payment recipient with a bank account in Pagar.me, which sets up an entity that can receive financial transfers and payment splits. Creating recipients directly enables financial flows (payouts, splits) to designated bank accounts, making this a Financial category action. Misuse could redirect funds to unauthorized recipients.

From the tool's definition Cria um recipient (personal) no Pagar.me com conta bancária padrão

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pagarme_create_recipient Approval-gated

Any call to pagarme_create_recipient is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pagarme_create_recipient": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE 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_create_recipient

What does the pagarme_create_recipient tool do? +

Cria um recipient (personal) no Pagar.me com conta bancária padrão. It is categorised as a Financial tool in the Payments MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on pagarme_create_recipient? +

Register the Payments MCP server in PolicyLayer and add a rule for pagarme_create_recipient: 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_create_recipient? +

pagarme_create_recipient is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pagarme_create_recipient? +

Yes. Add a rate_limit block to the pagarme_create_recipient 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_create_recipient completely? +

Set action: deny in the PolicyLayer policy for pagarme_create_recipient. 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_create_recipient? +

pagarme_create_recipient 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.