List all loaded plugins and machine-readable plugin availability facts,
AI agents call list_plugins to retrieve information from Code-Index-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs introspection on the plugin system, returning a data structure about what plugins are available. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. It is a pure information retrieval operation, making it a Read category tool with low severity since disclosure of plugin availability poses minimal risk.
From the tool's definition The tool 'list_plugins' retrieves and lists currently loaded plugins along with machine-readable availability facts. The description indicates a read-only query operation that provides information without modifying any state.
Documented attack patterns abuse exactly the kind of access list_plugins gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Code-Index-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_plugins:
{
"version": "1",
"default": "deny",
"tools": {
"list_plugins": {}
}
}list_plugins 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 loaded plugins and machine-readable plugin availability facts,. It is categorised as a Read tool in the Code-Index-MCP MCP Server, which means it retrieves data without modifying state.
Register the Code-Index- 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 Code-Index-MCP. 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 Code-Index- MCP server (viperjuice/code-index-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Code-Index-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Code-Index-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.