Delete the current webhook subscription
AI agents call deleteWebhookSubscription to permanently remove resources in Hevy MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes webhook subscription configuration without reversibility. While not a direct data deletion (like deleting workout records would be), webhook subscriptions are persistent system configurations whose removal cannot be undone without reconfiguring. The 'Delete' operation and irreversible nature of configuration removal places this in the Destructive category rather than Write.
From the tool's definition Tool name contains 'delete' and description states 'Delete the current webhook subscription'. The action irreversibly removes a configured webhook subscription.
Attacks that exploit this kind of access
Delete the current webhook subscription. It is categorised as a Destructive tool in the Hevy MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hevy MCP Server MCP server in PolicyLayer and add a rule for deleteWebhookSubscription: 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 Hevy MCP Server. Nothing to install.
deleteWebhookSubscription 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 deleteWebhookSubscription 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 deleteWebhookSubscription. 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.
deleteWebhookSubscription is provided by the Hevy MCP Server MCP server (jcjiron/hevy-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 →