Remove a registered webhook.
AI agents call trade.hooks.delete to permanently remove resources in Rekko MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a registered webhook, which is an irreversible destructive action. While the blast radius is limited (no financial transactions or data destruction beyond the webhook registration itself), it could disrupt automated trading signals or alerts if misused, warranting medium severity.
From the tool's definition 'Remove a registered webhook' and tool name 'trade.hooks.delete' — deletion of a registered resource is irreversible
Attacks that exploit this kind of access
Remove a registered webhook. It is categorised as a Destructive tool in the Rekko MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rekko MCP server in PolicyLayer and add a rule for trade.hooks.delete: 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 Rekko MCP. Nothing to install.
trade.hooks.delete 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 trade.hooks.delete 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 trade.hooks.delete. 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.
trade.hooks.delete is provided by the Rekko MCP server (rekko-ai/rekko-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 →