list_recipients

List all saved payment recipients. Shows names and masked account numbers.

SERVERAgentpay SOURCEagentpay-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/agentpay/list-recipients.md

WHAT IT DOES

What list_recipients does on Agentpay

AI agents call list_recipients to retrieve information from Agentpay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_recipients is rated Low

This is a Read operation: it queries and retrieves data (recipient list and account identifiers) without side effects. However, severity is medium rather than low because payment recipient information is sensitive financial data whose exposure could facilitate fraud or unauthorized transfers if an agent misuses the list output to initiate payments to attacker-controlled accounts.

From the tool's definition Tool description states it 'List[s] all saved payment recipients' with 'names and masked account numbers' — a retrieval operation with no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_recipients safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agentpay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_recipients, this is the rule to start with:

list_recipients Allowed

list_recipients is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_recipients": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agentpay, apply this rule, and every list_recipients call is checked against it from then on.

FAQ

Questions about list_recipients

What does the list_recipients tool do? +

List all saved payment recipients. Shows names and masked account numbers. It is categorised as a Read tool in the Agentpay MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_recipients? +

Register the Agentpay MCP server in PolicyLayer and add a rule for list_recipients: 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 Agentpay. Nothing to install.

What risk level is list_recipients? +

list_recipients is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_recipients? +

Yes. Add a rate_limit block to the list_recipients 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.

How do I block list_recipients completely? +

Set action: deny in the PolicyLayer policy for list_recipients. 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 list_recipients? +

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

KEEP EXPLORING

More on Agentpay, and thousands of servers like it.

This server

All 17 Agentpay tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →