AI agents call get_transfer to retrieve information from SpherePay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries existing transfer data. It does not create, modify, execute, delete, or commit any financial transactions. While it accesses financial context data, the tool itself performs no financial operations—it is purely informational. The severity is low because reading historical transfer details poses minimal risk if misused by an AI agent.
From the tool's definition Tool name is 'get_transfer' and description states 'Retrieve a SpherePay transfer by ID. Returns transfer details including status.' This is a data retrieval operation with no modification or execution of actions.
Attacks that exploit this kind of access
Retrieve a SpherePay transfer by ID. Returns transfer details including status. It is categorised as a Read tool in the SpherePay MCP Server, which means it retrieves data without modifying state.
Register the SpherePay MCP server in PolicyLayer and add a rule for get_transfer: 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 SpherePay. Nothing to install.
get_transfer 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_transfer 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_transfer. 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_transfer is provided by the SpherePay MCP server (danchev/spherepay-mcp). 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 →