get_job_output
Get current accumulated stdout/stderr and status of a background job started with execute_bash_background or execute_bpftrace_background.
This record as markdown: /tools/42research-dynamic-mcp/get-job-output.md
What get_job_output does on Dynamic MCP Server
AI agents call get_job_output to retrieve information from Dynamic MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_job_output is rated Low
This tool only reads and returns accumulated output and status from background jobs that were already initiated by other tools. It has no side effects, does not modify data, and does not execute code.
From the tool's definition Tool description states it 'Get[s] current accumulated stdout/stderr and status' — purely retrieves output from previously-launched background jobs. No modification, deletion, or command execution.
Attacks that exploit this kind of access
The rule that runs get_job_output safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dynamic MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_job_output, this is the rule to start with:
get_job_output is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dynamic MCP Server, apply this rule, and every get_job_output call is checked against it from then on.
Questions about get_job_output
Get current accumulated stdout/stderr and status of a background job started with execute_bash_background or execute_bpftrace_background. It is categorised as a Read tool in the Dynamic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dynamic MCP Server MCP server in PolicyLayer and add a rule for get_job_output: 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 Dynamic MCP Server. Nothing to install.
get_job_output 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_output 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_output. 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_output is provided by the Dynamic MCP Server MCP server (42research/dynamic_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dynamic MCP Server, and thousands of servers like it.
This server
Across the catalogue