Agent Orchestration

35 tools. 19 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated:

19 can modify or destroy data
16 read-only
35 tools total

Community server · catalogue entry verified 12/06/2026

How to control Agent Orchestration ↓

What Agent Orchestration exposes to your agents

Read (16) Write / Execute (17) Destructive / Financial (2)
Critical Risk

The most dangerous Agent Orchestration tools

19 of Agent Orchestration's 35 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Agent Orchestration

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

Deny destructive operations
{
  "memory_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "claim_todo": {
    "limits": [
      {
        "counter": "claim_todo_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "agent_list": {
    "limits": [
      {
        "counter": "agent_list_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Agent Orchestration — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON AGENT ORCHESTRATION →

Free to start. No card required.

All 35 Agent Orchestration tools

WRITE 14 tools
Write claim_todo FOR SUB-AGENTS: Register yourself AND claim a specific task in one call. Use this when you were spawned to wor Write cursor_delegate_task Delegate a task to Cursor CLI and store session metadata for later resume/sync. Write cursor_sync_task Refresh a delegated Cursor task, sync the latest provider status, and persist knowledge back into shared memor Write research_ready Mark research as complete for a task. Validates that all required research items are documented based on task Write task_claim Claim a task to work on it. Sets status to in_progress. Requires research to be complete for non-trivial tasks Write agent_heartbeat Send a heartbeat to indicate agent is still active. Call periodically during long operations. Write agent_register Register this agent with the orchestration system. Call this at the start of your session. Write cursor_handoff_task Write a structured handoff for a delegated Cursor task so the next agent can resume with shared context. Write lock_release Release a lock you are holding. Write memory_set Store a value in shared memory. Use namespaces to organize: context, decisions, findings, blockers. Write task_complete Mark a task as completed with optional output. Write task_create Create a new task in the task queue. Complexity is auto-detected from title/description but can be overridden. Write task_generate_doc Generate or refresh the Markdown documentation for a task using current orchestration state. Write task_update Update a task status or progress.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Agent Orchestration

Can an AI agent delete data through the Agent Orchestration MCP server? +

Yes. The Agent Orchestration server exposes 2 destructive tools including memory_delete, agent_unregister. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Agent Orchestration? +

The Agent Orchestration server has 14 write tools including claim_todo, cursor_delegate_task, cursor_sync_task. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Agent Orchestration.

How many tools does the Agent Orchestration MCP server expose? +

35 tools across 4 categories: Destructive, Execute, Read, Write. 16 are read-only. 19 can modify, create, or delete data.

How do I enforce a policy on Agent Orchestration? +

Register the Agent Orchestration MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Agent Orchestration tool call.

Deterministic rules across all 35 Agent Orchestration tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

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.