Add jobs to your application queue by URL. Just paste the job posting URLs — title, company, and ATS are auto-detected. Supported: Ashby, Lever, SmartRecruiters, Workable, Greenhouse, Workday.
AI agents use add_to_queue to create or update resources in Shortlist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shortlist MCP Server environment.
The tool creates or adds data to a user's job queue—a write operation. Severity is medium because: (1) it's reversible (queue entries can be removed via clear_queue or similar tools), (2) the blast radius is limited to the user's own job application pipeline, and (3) misuse would result in unwanted jobs in the queue but not financial loss, data deletion, or code execution.
From the tool's definition Tool description states it 'Add jobs to your application queue' and mentions auto-detection of job posting data. This creates new queue entries (writes data to the user's job application queue).
Documented attack patterns abuse exactly the kind of access add_to_queue gives an agent:
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 add_to_queue:
{
"version": "1",
"default": "deny",
"tools": {
"add_to_queue": {
"limits": [
{
"counter": "add_to_queue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_to_queue stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add jobs to your application queue by URL. Just paste the job posting URLs — title, company, and ATS are auto-detected. Supported: Ashby, Lever, SmartRecruiters, Workable, Greenhouse, Workday. It is categorised as a Write tool in the Shortlist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shortlist MCP Server MCP server in PolicyLayer and add a rule for add_to_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.
add_to_queue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_to_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.
Set action: deny in the PolicyLayer policy for add_to_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.
add_to_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.
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.