Delete a webhook by its ID
AI agents call deleteWebhook to permanently remove resources in AMOCA Solana MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on webhook configurations. While not involving financial transactions or code execution, deletion of webhooks could disrupt monitoring, notification systems, or automated blockchain event tracking depending on how webhooks are used in the Solana ecosystem. Misuse by an AI agent could remove critical infrastructure monitoring, fitting the Destructive category.
From the tool's definition Tool name 'deleteWebhook' combined with description 'Delete a webhook by its ID' indicates irreversible deletion of data. Webhooks are configured integrations that, once deleted, cannot be recovered without manual reconfiguration.
Attacks that exploit this kind of access
Delete a webhook by its ID. It is categorised as a Destructive tool in the AMOCA Solana MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AMOCA Solana MCP Server MCP server in PolicyLayer and add a rule for deleteWebhook: 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 AMOCA Solana MCP Server. Nothing to install.
deleteWebhook is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteWebhook 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 deleteWebhook. 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.
deleteWebhook is provided by the AMOCA Solana MCP Server MCP server (manolaz/amoca-solana-mcp-server). 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 →