clear_queue

THE RISK

Critical Risk

Why clear_queue needs a policy

This operation permanently deletes an entire queue of job applications managed by the user. It cannot be undone and eliminates all pending work in one action. While not a financial tool per se, the loss of queued applications (which represent time and effort invested in the application pipeline) constitutes irreversible data destruction. The 'all' qualifier indicates a destructive, high-impact bulk operation.

From the tool's definition 'Clear all jobs from your application queue' — the tool irreversibly removes all queued job applications in bulk without granular selection or recovery mechanism.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control clear_queue

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 clear_queue:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_queue"
  ]
}

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

Create a free account and register Shortlist MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Shortlist MCP Server tools

Destructive delete_education Delete an education entry by ID. Get the ID from get_profile. Destructive delete_resume Delete a resume by ID. Get the ID from list_resumes. Destructive delete_work_experience Delete a work experience or project by ID. Get the ID from get_profile. Destructive remove_from_queue Remove a specific job from your application queue by its ID. Destructive remove_languages Remove one or more languages from your profile by name. Destructive remove_skills Remove one or more skills from your profile by name. Execute start_applying Start the bot to submit all approved job applications. The bot fills out forms and submits Execute stop_applying Stop the bot from submitting more applications.

All 32 Shortlist MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Shortlist MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clear_queue

What does the clear_queue tool do? +

Clear all jobs from your application queue. 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 clear_queue? +

Register the Shortlist MCP Server MCP server in PolicyLayer and add a rule for clear_queue: 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 clear_queue? +

clear_queue 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 clear_queue? +

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

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

clear_queue 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.

CHECK YOUR STACK →