get_recipient_requirements
AI agents call get_recipient_requirements 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 appears to retrieve or query information about recipient requirements (e.g., required fields for different countries/currencies) needed for the recipient creation process. It has no side effects and does not modify, execute, delete, or move money. It fits the Read category despite the empty description, as the naming convention strongly suggests data retrieval.
From the tool's definition Tool name 'get_recipient_requirements' suggests retrieval of data about requirements for recipients. The verb 'get' and lack of any modification language indicate a read operation. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
get_recipient_requirements. 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 get_recipient_requirements: 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.
get_recipient_requirements 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 get_recipient_requirements 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 get_recipient_requirements. 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.
get_recipient_requirements 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 →