AI agents call get_event 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 queries and returns event data (type, payload, webhook delivery records) without creating, modifying, deleting, or executing operations. It is a straightforward data retrieval operation with no destructive or financial implications. The low severity reflects minimal blast radius: an attacker could read event logs but cannot modify accounts, execute transfers, or cause financial harm.
From the tool's definition Tool name 'get_event' and description 'Retrieve a SpherePay event by ID' — the verb 'Retrieve' combined with the read-only operation of fetching event details by ID indicates data retrieval without modification or side effects.
Attacks that exploit this kind of access
Retrieve a SpherePay event by ID. Returns event details including type, payload, and webhook delivery records. 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_event: 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_event 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_event 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_event. 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_event 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 →