Approve a single job for application submission. Optionally provide form answers as JSON.
AI agents use approve_job 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 modifies state by approving and submitting a job application, which creates new data in external systems (job application platforms). While the description does not explicitly use words like 'submit' or 'create,' the context that this MCP server 'automate submissions across major platforms' makes clear this tool triggers application submission.
From the tool's definition Tool description states 'Approve a single job for application submission.' The context indicates it submits job applications 'across major platforms like Lever and Ashby.' This action creates a tangible application record on external platforms.
Documented attack patterns abuse exactly the kind of access approve_job 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 approve_job:
{
"version": "1",
"default": "deny",
"tools": {
"approve_job": {
"limits": [
{
"counter": "approve_job_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} approve_job 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.
Approve a single job for application submission. Optionally provide form answers as JSON. 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 approve_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 Shortlist MCP Server. Nothing to install.
approve_job 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 approve_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.
Set action: deny in the PolicyLayer policy for approve_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.
approve_job 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.