Get log output from a running or completed job.
AI agents call get_job_log to retrieve information from SPIRED-Stab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical log output without side effects or the ability to modify or execute operations. It falls squarely into the Read category. The severity is low because log data retrieval poses minimal security risk—logs are diagnostic output that do not affect system state or data integrity. The confidence is high because the description unambiguously indicates a read-only query operation.
From the tool's definition The tool description states it 'Get[s] log output from a running or completed job.' This is a read-only retrieval operation with no modification, deletion, or execution capability. It queries job state information.
Attacks that exploit this kind of access
Get log output from a running or completed job. It is categorised as a Read tool in the SPIRED-Stab MCP MCP Server, which means it retrieves data without modifying state.
Register the SPIRED-Stab MCP server in PolicyLayer and add a rule for get_job_log: 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 SPIRED-Stab MCP. Nothing to install.
get_job_log 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_log 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_log. 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_log is provided by the SPIRED-Stab MCP server (macromnex/spired_stab_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 →