List all plugins with enabled/disabled status.
AI agents call list_plugins to retrieve information from Overlord MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only retrieval of plugin metadata. It queries the system state to enumerate plugins and their status, produces no side effects, and does not create, modify, delete, or execute anything. The blast radius of misuse is minimal—an attacker gains visibility into installed plugins but cannot directly compromise the system through this tool alone.
From the tool's definition Tool name is 'list_plugins' and description states 'List all plugins with enabled/disabled status' — a pure query operation that retrieves and displays plugin information without modification or side effects.
Attacks that exploit this kind of access
List all plugins with enabled/disabled status. It is categorised as a Read tool in the Overlord MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Overlord MCP Server MCP server in PolicyLayer and add a rule for list_plugins: 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 Overlord MCP Server. Nothing to install.
list_plugins 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_plugins 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_plugins. 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_plugins is provided by the Overlord MCP Server MCP server (skeeminator/overlord-mcp). 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 →