list_plugins
[MAINTENANCE] Read-only: Lightweight index of active tunnel plugins — name, description, enabled state, and tool_count. Does NOT return full tool schemas (use get_plugin_details for that). Dramatically reduces context bloat vs. dumping all plugin schemas at startup (~500 tokens vs 50k+). Returns ...
This record as markdown: /tools/io-github-ajc3xc-meridian/list-plugins.md
What list_plugins does on Meridian
AI agents call list_plugins to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_plugins is rated Low
This tool queries and retrieves metadata about active plugins without causing any side effects, modifications, or state changes. It is explicitly marked read-only and serves an informational purpose. The low severity reflects that exposing plugin metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'list_plugins' and description explicitly states 'Read-only' and 'Lightweight index of active tunnel plugins — name, description, enabled state, and tool_count.' Returns data without modification: 'Returns an 'active_plugins' list plus any stored…
Attacks that exploit this kind of access
The rule that runs list_plugins safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_plugins, this is the rule to start with:
list_plugins is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every list_plugins call is checked against it from then on.
Questions about list_plugins
[MAINTENANCE] Read-only: Lightweight index of active tunnel plugins — name, description, enabled state, and tool_count. Does NOT return full tool schemas (use get_plugin_details for that). Dramatically reduces context bloat vs. dumping all plugin schemas at startup (~500 tokens vs 50k+). Returns an 'active_plugins' list plus any stored skill notes. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
Register the Meridian 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 Meridian. 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 Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue