// SCAN REPORT

OrgX

29 tools. 16 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 10 Jun 2026

16 can modify or destroy data

13 read-only

29 tools total

Community server · catalogue entry verified 10/06/2026 · full schemas captured for 29 of 29 tools

How to control OrgX ↓

TOOL MAP

Read (13) Write / Execute (15) Destructive / Financial (1)

CONTEXT-WINDOW COST

24,130 tokens of tool definitions, loaded on every request

12% of a 200k context window

2,682 heaviest tool: scaffold_initiative

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

Destructive · High orgx_act Run a lifecycle, validation, completion, or proof action on one OrgX entity. Per-action required inputs: • update → "fields" patch object. Execute · Medium handoff_task Reassign work to another specialist AI agent and optionally spawn a new run. Also known as: handoff task, transfer work, change assignee. US Execute · Medium orgx_emit_activity Emit append-only run telemetry for OrgX control-plane reporting. USE WHEN: agent is executing and needs to report progress. NEXT: Continue w Execute · Medium recommend_next_action Recommend what should happen next based on progress gaps, blockers, and execution templates. Also known as: next best action, prioritize wor

16 of OrgX's 29 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL ORGX

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

Deny destructive operations

{
  "orgx_act": {
    "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

{
  "approve_agent_work": {
    "limits": [
      {
        "counter": "approve_agent_work_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "consolidate_pr": {
    "limits": [
      {
        "counter": "consolidate_pr_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Create a free account and register OrgX — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ORGX →

Free to start. No card required.

ALL 29 ORGX TOOLS

DESTRUCTIVE 1 tools

Destructive orgx_act Run a lifecycle, validation, completion, or proof action on one OrgX entity. Per-action required inputs: • u

EXECUTE 5 tools

Execute handoff_task Reassign work to another specialist AI agent and optionally spawn a new run. Also known as: handoff task, tran Execute orgx_emit_activity Emit append-only run telemetry for OrgX control-plane reporting. USE WHEN: agent is executing and needs to rep Execute recommend_next_action Recommend what should happen next based on progress gaps, blockers, and execution templates. Also known as: ne Execute scaffold_initiative Turn an objective, roadmap, launch, or feature plan into executable workstreams, milestones, and tasks. Also k Execute spawn_agent_task Delegate work to a specialist AI agent and track the assigned task. Also known as: hand this off, assign task,

WRITE 10 tools

Write approve_agent_work Review or act on agent decisions awaiting human approval. Also known as: pending approvals, agent blocked, sig Write approve_decision Approve a pending agent decision after explicit user confirmation. Also known as: sign off, approve AI work, u Write delegate_agent_task Assign work to a specialist AI agent and track the result. Also known as: hand this off, spawn agent, assign t Write orgx_attach Attach a durable artifact, proof URL, or preview to an existing OrgX entity. USE WHEN: saving evidence, PRs, d Write orgx_decide Create, approve, reject, remember, or list durable OrgX decisions. Per-action input requirements: • action= Write orgx_plan Start, resume, edit, improve, or complete a tracked OrgX planning session. Per-action input requirements: • Write orgx_spawn Guard, estimate, classify, spawn, or hand off specialist agent work. Inputs: spawn from task REQUIRES task_id Write orgx_submit_receipt Submit a durable receipt (proof, outcome, quality, attribution, or learning) anchored to an OrgX entity or art Write orgx_write Create or update one OrgX record (snake_case fields). Create needs: initiative title; workstream title+initia Write reject_decision Reject a pending agent decision with guidance after explicit user confirmation. Also known as: request revisio

READ 13 tools

Read consolidate_pr Generate and persist an orchestration.consolidation_pass receipt for a GitHub pull request. USE WHEN: Eli or a Read get_agent_status Show current AI agent activity, blocked work, and execution state. Also known as: agent status, what agents ar Read get_initiative_pulse Get project health, blockers, milestones, owners, and recent activity for an initiative. Also known as: projec Read get_morning_brief Curated receipts, exceptions, ROI delta, and value signals from the most recent autonomous session. The brief Read get_operator_chronicle Read the operator chronicle: decision chronology, yesterday/week/30-day rollups, reportingNarrative.briefMarkd Read orgx_bootstrap Establish OrgX session context, discover granted scopes, and get the v2 tool routing map. Also known as: boots Read orgx_inspect Hydrate one OrgX entity with execution context. USE WHEN: the user names a specific task, milestone, initiativ Read orgx_recommend Recommend next work, summarize operator-chronicle/morning-brief signals, or read prioritization context. USE W Read orgx_search Find OrgX entities, decisions, artifacts, and memory. USE WHEN: browsing work, searching memory, finding IDs, Read query_org_memory Search team memory, organizational decisions, prior artifacts, and project context across agents. Also known a Read recall_memory Search organizational memory for prior decisions, artifacts, project context, and team knowledge. Also known a Read review_artifact Surface the next artifact awaiting review. Renders the artifact-review widget with a preview, version filmstri Read track_project_progress Get health, blockers, milestones, owners, and recent activity for a project or initiative. Also known as: proj

RELATED SERVERS

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

FAQ

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

Yes. The OrgX server exposes 1 destructive tools including orgx_act. 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 OrgX? +

The OrgX server has 10 write tools including approve_agent_work, approve_decision, delegate_agent_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 OrgX.

How many tools does the OrgX MCP server expose? +

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

How do I enforce a policy on OrgX? +

Register the OrgX 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 OrgX tool call.

Deterministic rules across all 29 OrgX tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ORGX →

Free to start. No card required.

29 OrgX tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

OrgX

// TOOL MAP

// CONTEXT-WINDOW COST

// MOST DANGEROUS TOOLS

// HOW TO CONTROL ORGX

// ALL 29 ORGX TOOLS

// RELATED SERVERS

// FAQ