Retrieve a beneficiary by id. Returns bank details, entity_type, and allowed payment_methods.
AI agents call retrieve_beneficiary to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only fetches existing beneficiary information without creating, modifying, deleting, or executing payments. Although the context is payment-related (AP2 protocol), the tool itself performs read-only data retrieval. Exposure of bank details is a concern, but the tool's functional category is Read.
From the tool's definition Tool retrieves data (bank details, entity_type, allowed payment_methods) by ID. The name 'retrieve_beneficiary' and description 'Retrieve a beneficiary' indicate a query/lookup operation with no modification or financial transaction initiated.
Documented attack patterns abuse exactly the kind of access retrieve_beneficiary 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 retrieve_beneficiary:
{
"version": "1",
"default": "deny",
"tools": {
"retrieve_beneficiary": {}
}
}retrieve_beneficiary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve a beneficiary by id. Returns bank details, entity_type, and allowed payment_methods. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for retrieve_beneficiary: 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.
retrieve_beneficiary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the retrieve_beneficiary 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 retrieve_beneficiary. 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.
retrieve_beneficiary 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.