AI agents call list_plans to retrieve information from Tpc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of existing plans without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk, suitable for information gathering only.
From the tool's definition Tool name 'list_plans' and description 'List all plans in the TPC system' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all plans in the TPC system. It is categorised as a Read tool in the Tpc MCP Server, which means it retrieves data without modifying state.
Register the Tpc 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 Tpc. 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 Tpc MCP server (suttonwilliamd/tpc-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →