list_recipients
AI agents call list_recipients to retrieve information from Wise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves recipient data without modifying it, making it a Read operation. However, severity is elevated to medium because recipient lists in financial systems (Wise is a money transfer platform) can contain sensitive personal and banking information that could be misused if accessed by unauthorized agents or leaked through prompt injection. The empty tool description reduces confidence slightly.
From the tool's definition Tool name 'list_recipients' indicates a retrieval operation. The server description mentions 'listing recipients' as a core capability. No description provided for the tool itself, limiting specificity.
Attacks that exploit this kind of access
list_recipients. It is categorised as a Read tool in the Wise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wise 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 Wise MCP Server. Nothing to install.
list_recipients 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_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.
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.
list_recipients is provided by the Wise MCP Server MCP server (rkm7448/mcp-wise). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →