Get the current status of a previously executed async command/task
AI agents call get_task_status to retrieve information from MCP OpenClaw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about an asynchronous task that was previously executed. It performs a read-only query with no side effects, no data modification, and no command execution. The low severity reflects minimal blast radius—an agent misusing this tool could only retrieve unwanted status information, not cause destructive or financial harm.
From the tool's definition Tool name 'get_task_status' and description 'Get the current status of a previously executed async command/task' indicate a query operation that retrieves status information without modifying or executing anything.
Attacks that exploit this kind of access
Get the current status of a previously executed async command/task. It is categorised as a Read tool in the MCP OpenClaw MCP Server, which means it retrieves data without modifying state.
Register the MCP OpenClaw MCP server in PolicyLayer and add a rule for get_task_status: 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 OpenClaw. Nothing to install.
get_task_status 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_status 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_status. 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_status is provided by the MCP OpenClaw MCP server (starlink-awaken/mcp-openclaw). 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 →