delete_standing_intent
Permanently retire a registered standing intent (webhook watch) by intent_id — deliveries stop and the watch cannot be recovered. Requires a key. Get the intent_id from list_standing_intents or from the register response. Answers "stop watching this". Do NOT use to pause temporarily; there is no ...
This record as markdown: /tools/cloud-dchub-mcp-server/delete-standing-intent.md
What delete_standing_intent does on Mcp Server
AI agents call delete_standing_intent to permanently remove resources in Mcp Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
intent_id | string | Yes | The intent_id to delete (from list_standing_intents or register) |
Parameters from the server's own tool schema.
Why delete_standing_intent is rated Critical
Irreversibly deletes webhook registration with no undo or recovery option available.
From the tool's definition Permanently retire, cannot be recovered, watch cannot be recovered.
Attacks that exploit this kind of access
The rule that runs delete_standing_intent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_standing_intent, this is the rule to start with:
delete_standing_intent is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every delete_standing_intent call is checked against it from then on.
Questions about delete_standing_intent
Permanently retire a registered standing intent (webhook watch) by intent_id — deliveries stop and the watch cannot be recovered. Requires a key. Get the intent_id from list_standing_intents or from the register response. Answers "stop watching this". Do NOT use to pause temporarily; there is no pause, this removes the watch. It is categorised as a Destructive tool in the Mcp Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_standing_intent accepts 1 parameter: intent_id. Required: intent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for delete_standing_intent: 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 Mcp Server. Nothing to install.
delete_standing_intent 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_standing_intent 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_standing_intent. 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_standing_intent is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
Across the catalogue