Start the bot to submit all approved job applications. The bot fills out forms and submits them automatically.
AI agents invoke start_applying to trigger actions in Shortlist MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an automated workflow that sends data to external job application platforms and commits actions (form submissions) that have real-world consequences. While the applications are pre-approved, the tool triggers irreversible submissions to third-party systems.
From the tool's definition Tool description states it will "submit all approved job applications" and "fills out forms and submits them automatically." The action of submitting applications across external platforms (Lever, Ashby) constitutes triggering external operations whose…
Documented attack patterns abuse exactly the kind of access start_applying 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 start_applying:
{
"version": "1",
"default": "deny",
"tools": {
"start_applying": {
"limits": [
{
"counter": "start_applying_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_applying stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Start the bot to submit all approved job applications. The bot fills out forms and submits them automatically. It is categorised as a Execute tool in the Shortlist MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Shortlist MCP Server MCP server in PolicyLayer and add a rule for start_applying: 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.
start_applying is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_applying 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 start_applying. 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.
start_applying 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.