Retrieves the stdout of a running background task.
AI agents call get-task-stdout to retrieve information from MCP Background Task Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns output logs from an already-running background task. Retrieval operations with no capacity to modify, delete, execute new code, or trigger external side effects are classified as Read. The blast radius is minimal—reading task output cannot harm system state unless that output itself contains sensitive data, but that is an information exposure risk rather than a tool-capability risk.
From the tool's definition Tool name 'get-task-stdout' and description 'Retrieves the stdout of a running background task' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Retrieves the stdout of a running background task. It is categorised as a Read tool in the MCP Background Task Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Background Task Server MCP server in PolicyLayer and add a rule for get-task-stdout: 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 Background Task Server. Nothing to install.
get-task-stdout 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-task-stdout 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-task-stdout. 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-task-stdout is provided by the MCP Background Task Server MCP server (nanoseil/mcp-bgtask). 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 →