Get the full result of a task including stdout/stderr output.
AI agents call get-task-result to retrieve information from Back-Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reads task output (stdout/stderr) that has already been generated. It is a query/get operation with no capability to modify, delete, execute, or commit financial changes. The sibling tool 'execute-task' would handle execution; this one only reads results.
From the tool's definition Tool name is 'get-task-result' and description states it 'Get the full result of a task including stdout/stderr output' — purely retrieval of existing task results without modification or side effects.
Attacks that exploit this kind of access
Get the full result of a task including stdout/stderr output. It is categorised as a Read tool in the Back-Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Back-Agent MCP Server MCP server in PolicyLayer and add a rule for get-task-result: 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 Back-Agent MCP Server. Nothing to install.
get-task-result 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-result 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-result. 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-result is provided by the Back-Agent MCP Server MCP server (zuens2020/back-agent-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 →