Check status of a running analysis job
AI agents call get_job_status to retrieve information from Mcp Log Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of an existing job, which is a retrieval operation with no side effects. It does not create, modify, delete, or execute code. The confidence is high because the description clearly indicates a status-checking (read) operation, though confidence is not absolute because the scope of what constitutes 'job status' information is not detailed.
From the tool's definition Tool name 'get_job_status' and description 'Check status of a running analysis job' indicate a read-only query operation that retrieves current state information without modifying or executing anything.
Attacks that exploit this kind of access
Check status of a running analysis job. It is categorised as a Read tool in the Mcp Log Analyzer MCP Server, which means it retrieves data without modifying state.
Register the Mcp Log Analyzer 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 Mcp Log Analyzer. 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 Mcp Log Analyzer MCP server (mashish/nft-log-analyzer). 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 →