delete_workflow_template
Delete a custom workflow template the caller owns. Built-in templates cannot be deleted. This removes the saved definition; runs already started from it are unaffected. Requires authentication and the workflows:write scope.
This record as markdown: /tools/com-meta-council-decision-intelligence/delete-workflow-template.md
What delete_workflow_template does on Meta Council
AI agents call delete_workflow_template to permanently remove resources in Meta Council, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | Slug of the template to delete, from list_workflows. |
expected_template_fingerprint | string | — | Optional. The definition fingerprint you last saw for this template, returned by update_workflow_template when it last succeeded. Supply it and the write refuse |
Parameters from the server's own tool schema.
Why delete_workflow_template is rated Critical
An AI agent that decides to call delete_workflow_template doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Meta Council is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_workflow_template safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_workflow_template, this is the rule to start with:
delete_workflow_template 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 Meta Council, apply this rule, and every delete_workflow_template call is checked against it from then on.
Questions about delete_workflow_template
Delete a custom workflow template the caller owns. Built-in templates cannot be deleted. This removes the saved definition; runs already started from it are unaffected. Requires authentication and the workflows:write scope. It is categorised as a Destructive tool in the Meta Council MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_workflow_template accepts 2 parameters: slug, expected_template_fingerprint. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for delete_workflow_template: 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 Meta Council. Nothing to install.
delete_workflow_template 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_workflow_template 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_workflow_template. 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_workflow_template is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
Across the catalogue