List beneficiaries. Supports pagination and filters by entity_type, nickname and bank_country_code.
AI agents call list_beneficiaries 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 retrieves and queries beneficiary information without modifying, deleting, or executing operations. It supports filtering and pagination but does not create, update, delete, or move money. While the AP2 context involves payments, this specific tool only reads beneficiary data, making it a Read category tool with low severity since it has no destructive or financial side effects.
From the tool's definition Tool name 'list_beneficiaries' and description indicate data retrieval only: 'List beneficiaries' with 'Supports pagination and filters' — classic read operation patterns (list, filter, paginate).
Documented attack patterns abuse exactly the kind of access list_beneficiaries 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 list_beneficiaries:
{
"version": "1",
"default": "deny",
"tools": {
"list_beneficiaries": {}
}
}list_beneficiaries 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.
List beneficiaries. Supports pagination and filters by entity_type, nickname and bank_country_code. 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 list_beneficiaries: 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.
list_beneficiaries 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 list_beneficiaries 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 list_beneficiaries. 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.
list_beneficiaries 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.