Fetch a downstream MCP task result and apply the same output
AI agents call gateway.tasks_result to retrieve information from PMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the result of a previously executed task from a downstream MCP server. It queries and returns data without side effects, making it a Read operation. The blast radius is low since it only accesses already-computed results. The 'apply the same output' phrasing refers to presenting/returning the result, not executing or modifying it.
From the tool's definition Tool name and description indicate 'Fetch a downstream MCP task result and apply the same output' — retrieves data from a task execution without modifying or deleting anything. The verb 'Fetch' is characteristic of Read operations.
Documented attack patterns abuse exactly the kind of access gateway.tasks_result gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for gateway.tasks_result:
{
"version": "1",
"default": "deny",
"tools": {
"gateway.tasks_result": {}
}
}gateway.tasks_result is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch a downstream MCP task result and apply the same output. It is categorised as a Read tool in the PMCP MCP Server, which means it retrieves data without modifying state.
Register the P MCP server in PolicyLayer and add a rule for gateway.tasks_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 PMCP. Nothing to install.
gateway.tasks_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 gateway.tasks_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 gateway.tasks_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.
gateway.tasks_result is provided by the P MCP server (viperjuice/pmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 PMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.