Critical Risk →

delete_resume

Delete a resume by ID. Get the ID from list_resumes.

How to control delete_resume ↓

What delete_resume does on Shortlist MCP Server

AI agents call delete_resume to permanently remove resources in Shortlist 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_resume needs a policy

This tool permanently removes resume data, which cannot be undone. Deletion is irreversible and constitutes a destructive action. While the blast radius is limited to the user's own resume data (not system-wide), the high confidence reflects the unambiguous destructive nature of the operation.

From the tool's definition Tool name 'delete_resume' with description 'Delete a resume by ID' explicitly performs an irreversible deletion operation.

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

How to control delete_resume

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

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

delete_resume 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 Shortlist 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_resume

What does the delete_resume tool do? +

Delete a resume by ID. Get the ID from list_resumes. It is categorised as a Destructive tool in the Shortlist 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_resume? +

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

What risk level is delete_resume? +

delete_resume 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_resume? +

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

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

delete_resume is provided by the Shortlist MCP Server MCP server (mls-tech-inc/shortlistjobs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Shortlist MCP Server tool call.

Start from Shortlist 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.

32 Shortlist 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.