Low Risk

cursor_task_status

Show the latest health, recovery state, and hints for a delegated Cursor task.

How to control cursor_task_status ↓

What cursor_task_status does on Agent Orchestration

AI agents call cursor_task_status to retrieve information from Agent Orchestration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why cursor_task_status needs a policy

This tool retrieves task metadata and status information without side effects. It does not create, modify, delete, or execute operations. The 'health, recovery state, and hints' are informational read-only queries about existing task state, consistent with the Read category. Severity is low because misuse results in information disclosure only, with no blast radius to system integrity or external operations.

From the tool's definition Tool queries state of a delegated task: 'Show the latest health, recovery state, and hints for a delegated Cursor task.' No write, delete, or execution of arbitrary code is performed—only retrieval and display of task status information.

Documented attack patterns abuse exactly the kind of access cursor_task_status gives an agent:

How to control cursor_task_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Orchestration, and nothing reaches the server without passing your rules. This is the rule we recommend for cursor_task_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cursor_task_status": {}
  }
}

cursor_task_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Agent Orchestration — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cursor_task_status

What does the cursor_task_status tool do? +

Show the latest health, recovery state, and hints for a delegated Cursor task. It is categorised as a Read tool in the Agent Orchestration MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cursor_task_status? +

Register the Agent Orchestration MCP server in PolicyLayer and add a rule for cursor_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 Agent Orchestration. Nothing to install.

What risk level is cursor_task_status? +

cursor_task_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cursor_task_status? +

Yes. Add a rate_limit block to the cursor_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.

How do I block cursor_task_status completely? +

Set action: deny in the PolicyLayer policy for cursor_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.

What MCP server provides cursor_task_status? +

cursor_task_status is provided by the Agent Orchestration MCP server (madebyaris/agent-orchestration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Orchestration tool call.

Start from Agent Orchestration, 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.

35 Agent Orchestration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.