Get the result of an async task (removes the task after retrieval)
AI agents call async_get_task_result to retrieve information from MCP Async Bridge Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool primarily reads/retrieves task result data. While it mentions removal after retrieval, that is an automatic consequence of the read operation (cleanup of processed task state), not a destructive action initiated by the user. It has no execution capabilities, cannot modify data reversibly, and poses minimal risk if misused by an agent—retrieving old task results carries low blast radius.
From the tool's definition Tool retrieves a task result with 'Get the result of an async task'. The removal after retrieval is an automatic cleanup mechanism, not a destructive user action.
Attacks that exploit this kind of access
Get the result of an async task (removes the task after retrieval). It is categorised as a Read tool in the MCP Async Bridge Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Async Bridge Server MCP server in PolicyLayer and add a rule for async_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 MCP Async Bridge Server. Nothing to install.
async_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 async_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 async_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.
async_get_task_result is provided by the MCP Async Bridge Server MCP server (mako10k/mcp-async). 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 →