Critical Risk →

delete_job

Delete a job by its ID

How to control delete_job ↓

What delete_job does on ElevenLabs MCP Server

AI agents call delete_job to permanently remove resources in ElevenLabs MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_job needs a policy

This tool permanently removes a job record from the ElevenLabs system. Deletion is irreversible and cannot be undone. While the blast radius is limited to job records (not financial transactions or system-wide data), it still constitutes destructive action. Severity is high because an AI agent with misuse could systematically wipe legitimate user jobs, disrupting workflows and data management.

From the tool's definition Tool name is 'delete_job' and description states 'Delete a job by its ID' — the verb 'delete' indicates irreversible removal of data.

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

How to control delete_job

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

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

delete_job 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 ElevenLabs MCP Server — 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_job

What does the delete_job tool do? +

Delete a job by its ID. It is categorised as a Destructive tool in the ElevenLabs MCP Server 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_job? +

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

What risk level is delete_job? +

delete_job 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_job? +

Yes. Add a rate_limit block to the delete_job 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_job completely? +

Set action: deny in the PolicyLayer policy for delete_job. 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_job? +

delete_job is provided by the ElevenLabs MCP Server MCP server (mamertofabian/elevenlabs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ElevenLabs MCP Server tool call.

Start from ElevenLabs MCP Server, 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.

6 ElevenLabs MCP Server 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.