AI agents call get_webhook 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.
The tool queries and returns existing webhook configuration data without side effects. It does not create, modify, delete, or trigger any financial transactions or code execution. This is a straightforward data retrieval operation, placing it in the Read category with low severity due to minimal blast radius if misused by an agent.
From the tool's definition Tool name is 'get_webhook' and description states 'Retrieve a SpherePay webhook by ID. Returns webhook details including delivery status and subscribed events.' This is a read-only retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Retrieve a SpherePay webhook by ID. Returns webhook details including delivery status and subscribed events. 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_webhook: 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_webhook 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_webhook 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_webhook. 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_webhook 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 →