Start, resume, edit, improve, or complete a tracked OrgX planning session. Per-action input requirements: • action="start" → REQUIRES feature_name. Optional: initial_plan (markdown to seed the session). • action="resume" → REQUIRES session_id. • action="improve" → REQUIRES session_id AND plan_con...
AI agents use orgx_plan to create or update resources in OrgX — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OrgX environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | — | Planning action to perform. See top-level description for per-action required fields. |
_context | object | — | Client context for conversation tracking (strongly recommended for cross-client continuity) |
attach_to | object | — | Optional target to link the completed plan to when action=complete. Shape: { entity_type: "initiative" | "workstream" | "task", entity_id: string }. |
session_id | string | — | Plan session UUID or orgx://plan_session/<uuid> URI. REQUIRED for action=resume | improve | record_edit | complete. Omit for action=start. |
edit_summary | string | — | One-line description of the change being recorded. REQUIRED when action=record_edit. |
feature_name | string | — | Feature or plan name. REQUIRED when action=start. |
initial_plan | string | — | Markdown plan content to seed the new session. Optional on action=start; the session can also be started empty and filled via improve/record_edit. |
plan_content | string | — | Current/final plan markdown. REQUIRED when action=improve (the draft to critique) or action=complete (the final accepted plan). |
idempotency_key | string | — | Optional idempotency key for safe retries. Same key returns the same result without creating duplicate session state. |
Parameters from the server's own tool schema.
An AI agent can call orgx_plan faster than any human can review — one bad instruction and it creates or modifies resources in OrgX by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (25 properties)
Documented attack patterns abuse exactly the kind of access orgx_plan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OrgX, and nothing reaches the server without passing your rules. This is the rule we recommend for orgx_plan:
{
"version": "1",
"default": "deny",
"tools": {
"orgx_plan": {
"limits": [
{
"counter": "orgx_plan_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}orgx_plan stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Start, resume, edit, improve, or complete a tracked OrgX planning session. Per-action input requirements: • action="start" → REQUIRES feature_name. Optional: initial_plan (markdown to seed the session). • action="resume" → REQUIRES session_id. • action="improve" → REQUIRES session_id AND plan_content (the current draft to critique). • action="record_edit" → REQUIRES session_id AND edit_summary (one-line description of the change). • action="complete" → REQUIRES session_id AND plan_content (the final accepted plan). Optional: attach_to (target entity to link the completed plan to). USE WHEN: work is still in planning or should become executable context. NEXT: use orgx_write or orgx_act after the plan is accepted and needs durable execution state. DO NOT USE WHEN: directly scaffolding a full initiative hierarchy; use scaffold_initiative for that compatibility path. It is categorised as a Write tool in the OrgX MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
orgx_plan accepts 9 parameters: action, _context, attach_to, session_id, edit_summary, feature_name, initial_plan, plan_content, idempotency_key. The full parameter table on this page comes from the server's own tool schema.
Register the OrgX MCP server in PolicyLayer and add a rule for orgx_plan: 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 OrgX. Nothing to install.
orgx_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the orgx_plan 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 orgx_plan. 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.
orgx_plan is provided by the OrgX MCP server (useorgx/orgx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 OrgX tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 OrgX tools catalogued and risk-classified — across an index of 42,500+ MCP servers.