Low Risk

list_recipients

Lists saved withdrawal recipients (payout beneficiaries).

How to control list_recipients ↓

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

Low Risk

This is fundamentally a Read operation — it queries and returns existing data without modifying or deleting anything. However, severity is elevated to 'medium' rather than 'low' because the returned data (withdrawal recipient details, payout beneficiaries) is financially sensitive.

From the tool's definition Tool name is 'list_recipients' and description states it 'Lists saved withdrawal recipients (payout beneficiaries)' — a retrieval operation with no modification.

Documented attack patterns abuse exactly the kind of access list_recipients gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and PayRam MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_recipients:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_recipients": {}
  }
}

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

  1. Create a free account and register PayRam MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_recipients tool do? +

Lists saved withdrawal recipients (payout beneficiaries). It is categorised as a Read tool in the PayRam MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_recipients? +

Register the PayRam MCP Server 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 PayRam MCP Server. 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 PayRam MCP Server MCP server (payram/payram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PayRam MCP Server tool call.

Deterministic rules across all 35 PayRam MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

35 PayRam MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.