Critical Risk →

delete_source

Delete a workflow source.

How to control delete_source ↓

What delete_source does on Automagik Tools

AI agents call delete_source to permanently remove resources in Automagik Tools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_source needs a policy

This tool permanently removes a workflow source, which cannot be undone. Deletion of data is irreversible and qualifies as destructive. The high severity reflects that an AI agent misusing this tool could remove critical workflow configurations, disrupting automation pipelines. Confidence is high because the description explicitly uses the word 'delete,' which unambiguously indicates destructive action.

From the tool's definition The tool name is 'delete_source' and the description states 'Delete a workflow source.' The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_source gives an agent:

How to control delete_source

PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_source:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_source"
  ]
}

delete_source disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Automagik Tools — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_source

What does the delete_source tool do? +

Delete a workflow source. It is categorised as a Destructive tool in the Automagik Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_source? +

Register the Automagik Tools MCP server in PolicyLayer and add a rule for delete_source: 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 Automagik Tools. Nothing to install.

What risk level is delete_source? +

delete_source is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_source? +

Yes. Add a rate_limit block to the delete_source 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.

How do I block delete_source completely? +

Set action: deny in the PolicyLayer policy for delete_source. 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.

What MCP server provides delete_source? +

delete_source is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Automagik Tools tool call.

Start from Automagik Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.