Open an existing plan. Use this at the start of a session when resuming prior work. Opening an archived plan automatically restores it to active. Returns the list of root tasks so you can pick up where you left off. All task tools operate on the open plan, so you must open one before doing any ta...
AI agents use open_plan to create or update resources in Conductor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Conductor environment.
While 'open_plan' sounds like a read operation, the description explicitly states it changes state: opening an archived plan restores it from archived to active status. This is a reversible state modification (Write), not merely a read. The severity is medium because misuse could inadvertently reactivate archived plans and set the active plan context for subsequent task operations.
From the tool's definition Opening an archived plan automatically restores it to active
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access open_plan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Conductor, and nothing reaches the server without passing your rules. This is the rule we recommend for open_plan:
{
"version": "1",
"default": "deny",
"tools": {
"open_plan": {
"limits": [
{
"counter": "open_plan_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}open_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.
Open an existing plan. Use this at the start of a session when resuming prior work. Opening an archived plan automatically restores it to active. Returns the list of root tasks so you can pick up where you left off. All task tools operate on the open plan, so you must open one before doing any task work. It is categorised as a Write tool in the Conductor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Conductor MCP server in PolicyLayer and add a rule for open_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 Conductor. Nothing to install.
open_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 open_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 open_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.
open_plan is provided by the Conductor MCP server (shannonbay/conductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Conductor, 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.
16 Conductor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.