Submit a structured plan proposal with a root task and child tasks.
AI agents use plan_proposal 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.
This tool creates and submits new plans and tasks, modifying the state of the task tree stored by the Conductor server. This is a Write operation because it creates new data reversibly (plans and tasks can presumably be archived, cancelled, or deleted via sibling tools like 'archive_plan' and 'agent_cancelled').
From the tool's definition Tool description states 'Submit a structured plan proposal with a root task and child tasks,' indicating creation of new plan and task data structures in the persistent task tree.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access plan_proposal 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 plan_proposal:
{
"version": "1",
"default": "deny",
"tools": {
"plan_proposal": {
"limits": [
{
"counter": "plan_proposal_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}plan_proposal 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.
Submit a structured plan proposal with a root task and child tasks. 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 plan_proposal: 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.
plan_proposal 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 plan_proposal 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 plan_proposal. 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.
plan_proposal 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.