Delete a specific webhook of a form.
AI agents call delete_form_webhook to permanently remove resources in JotForm API Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a webhook is an irreversible action that removes an integration endpoint from a form. This cannot be undone without recreating the webhook, potentially breaking downstream integrations or data pipelines that depend on it. This qualifies as Destructive with high severity due to the potential blast radius of silently severing automated workflows.
From the tool's definition "Delete a specific webhook of a form" — permanently removes a webhook integration
Attacks that exploit this kind of access
Delete a specific webhook of a form. It is categorised as a Destructive tool in the JotForm API Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the JotForm API Server MCP server in PolicyLayer and add a rule for delete_form_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 JotForm API Server. Nothing to install.
delete_form_webhook 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 delete_form_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 delete_form_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.
delete_form_webhook is provided by the JotForm API Server MCP server (the-ai-workshops/jotform-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 →