Get status and progress of an async job by ID with real-time accurate progress.
AI agents call get_job_status to retrieve information from Local Search 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 job status information—a pure read operation with no side effects, data modification, code execution, or destructive capability. The 'real-time accurate progress' phrasing confirms it observes state rather than changes it. Severity is low because misuse by an AI agent would only retrieve status data, posing minimal risk.
From the tool's definition Tool name 'get_job_status' and description 'Get status and progress of an async job by ID' indicate a read-only query operation that retrieves job metadata without modifying or executing anything.
Attacks that exploit this kind of access
Get status and progress of an async job by ID with real-time accurate progress. It is categorised as a Read tool in the Local Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Local Search MCP Server MCP server in PolicyLayer and add a rule for get_job_status: 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 Local Search MCP Server. Nothing to install.
get_job_status 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_status 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_status. 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_status is provided by the Local Search MCP Server MCP server (patrickruddiman/local-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →