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.
Despite the empty description, the naming convention and context within a financial server (Wise API) suggest this tool retrieves static or dynamic requirements/validation rules for recipients, rather than modifying state or executing transfers. This is a Read operation. Confidence is moderate (0.72) due to the missing description, but the tool name and server context provide sufficient evidence.
From the tool's definition Tool name 'get_recipient_requirements' indicates retrieval of data about recipient requirements. Server description mentions 'listing recipients' and 'validating account details' as read operations.
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 (sergeiledvanov/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 →