Medium Risk

save_recipient

Save a payment recipient's bank details for future transfers. The user provides the details once, then you can just say 'pay Maria' in the future.

Part of the Agentpay MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

agentpay-mcp-server Write Risk 2/5

AI agents use save_recipient to create or modify resources in Agentpay. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call save_recipient repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Agentpay.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

agentpay.yaml
tools:
  save_recipient:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Agentpay policy for all 17 tools.

Tool Name save_recipient
Category Write
MCP Server Agentpay MCP Server
Risk Level Medium

View all 17 tools →

Agents calling write-class tools like save_recipient have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the save_recipient tool do? +

Save a payment recipient's bank details for future transfers. The user provides the details once, then you can just say 'pay Maria' in the future.. It is categorised as a Write tool in the Agentpay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_recipient? +

Add a rule in your Intercept YAML policy under the tools section for save_recipient. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agentpay MCP server.

What risk level is save_recipient? +

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

Can I rate-limit save_recipient? +

Yes. Add a rate_limit block to the save_recipient rule in your Intercept 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 save_recipient completely? +

Set action: deny in the Intercept policy for save_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 save_recipient? +

save_recipient is provided by the Agentpay MCP server (agentpay-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Agentpay

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.