Get full details about a job in your queue — description, AI-filled answers, prefill status, and scraped form data.
AI agents call get_job_details to retrieve information from Shortlist MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries job information from a user's queue. It performs a read-only operation that returns job metadata, form data, and application status without creating, modifying, deleting, or executing any external actions. The data retrieved is informational only.
From the tool's definition Tool name 'get_job_details' and description 'Get full details about a job in your queue — description, AI-filled answers, prefill status, and scraped form data' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_job_details 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 get_job_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_job_details": {}
}
} get_job_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get full details about a job in your queue — description, AI-filled answers, prefill status, and scraped form data. It is categorised as a Read tool in the Shortlist MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shortlist MCP Server MCP server in PolicyLayer and add a rule for get_job_details: 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.
get_job_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_job_details 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 get_job_details. 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.
get_job_details 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.