List all saved plans with optional filtering.
AI agents call list_plans to retrieve information from Context Engine MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing plan metadata without creating, modifying, or deleting any data. The use of 'list' and 'filtering' are characteristic of read-only operations. Even if it exposes plan details, the blast radius from accidental misuse is minimal—it only returns information already stored in the system without altering state.
From the tool's definition Tool name 'list_plans' and description 'List all saved plans with optional filtering' indicate a query/retrieval operation with no side effects.
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 Context Engine MCP Server, 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 all saved plans with optional filtering. It is categorised as a Read tool in the Context Engine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Context Engine MCP Server 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 Context Engine MCP Server. 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 Context Engine MCP Server MCP server (kirachon/context-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Context Engine MCP Server, 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.
50 Context Engine MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.