List receivers onboarded under the current integrator account.
AI agents call list_receivers 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 or queries data (receivers in an integrator account) without modifying, deleting, or executing any operations. Even though it operates in a payment protocol context (AP2), listing existing receivers is a non-destructive read operation. The blast radius is low because exposing a list of receivers carries minimal risk compared to actually moving money or modifying payment configurations.
From the tool's definition Tool name is 'list_receivers' and description states it 'List receivers onboarded under the current integrator account.' The verb 'list' and the retrieval-oriented phrasing indicate a read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_receivers 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_receivers:
{
"version": "1",
"default": "deny",
"tools": {
"list_receivers": {}
}
}list_receivers 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 receivers onboarded under the current integrator account. 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_receivers: 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_receivers 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_receivers 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_receivers. 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_receivers 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.