Check the status and read live output of a background shell job. Use tail_lines to control how many lines to retrieve.
AI agents call shell_check_job to retrieve information from Hercules MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While this tool operates within a penetration testing context (Kali Linux environment), the specific capability is limited to querying and reading status/output of background processes—a Read operation with no side effects on the underlying system.
From the tool's definition The tool description explicitly states 'Check the status and read live output' and 'how many lines to retrieve', indicating data retrieval operations only. The name 'check_job' combined with 'read output' confirms non-destructive, read-only functionality.
Attacks that exploit this kind of access
Check the status and read live output of a background shell job. Use tail_lines to control how many lines to retrieve. It is categorised as a Read tool in the Hercules MCP MCP Server, which means it retrieves data without modifying state.
Register the Hercules MCP server in PolicyLayer and add a rule for shell_check_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 Hercules MCP. Nothing to install.
shell_check_job 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 shell_check_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 shell_check_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.
shell_check_job is provided by the Hercules MCP server (0xmihirk/hercules-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
shell_check_job is one line of Hercules's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →