List existing plans on the server. Call this at the start of every new session before creating anything — the work you need may already exist with progress recorded. Returns active plans by default; use status=
AI agents call list_plans to retrieve information from Conductor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward query/list operation that retrieves information about existing plans without side effects. It enables agents to discover pre-existing work before proceeding, which is a safe, read-only action. The low severity reflects minimal blast radius—misuse would only result in viewing task metadata, not modifying or executing tasks.
From the tool's definition Tool name 'list_plans' and description 'List existing plans on the server' clearly indicates a retrieval operation. The description explicitly states it 'Returns active plans' with no mention of modification, deletion, or execution of any kind.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list_plans 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 list_plans:
{
"version": "1",
"default": "deny",
"tools": {
"list_plans": {}
}
}list_plans is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List existing plans on the server. Call this at the start of every new session before creating anything — the work you need may already exist with progress recorded. Returns active plans by default; use status=. It is categorised as a Read tool in the Conductor MCP Server, which means it retrieves data without modifying state.
Register the Conductor MCP server in PolicyLayer and add a rule for list_plans: 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.
list_plans is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_plans 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 list_plans. 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.
list_plans 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.