Update a registered final beneficiary (name, document, country, type). referenceId is the path key and cannot be changed.
AI agents use update_recipient to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool creates or modifies beneficiary records within a payment/financial system. While it does not execute transactions or move funds directly, updating beneficiary information is a Write operation that affects critical financial identities. Severity is high because misuse could redirect payments to unauthorized recipients, though the operation itself is technically reversible (can be updated again).
From the tool's definition 'Update a registered final beneficiary' — modifies existing data records (name, document, country, type). The tool explicitly states it updates beneficiary information, which is reversible data modification.
Documented attack patterns abuse exactly the kind of access update_recipient gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for update_recipient:
{
"version": "1",
"default": "deny",
"tools": {
"update_recipient": {
"limits": [
{
"counter": "update_recipient_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_recipient 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.
Free to start. No card required.
Update a registered final beneficiary (name, document, country, type). referenceId is the path key and cannot be changed. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for update_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 Mcp Ap2. Nothing to install.
update_recipient is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_recipient is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.