get_plugin_details
[MAINTENANCE] Read-only: Full schema for one named plugin (all tool definitions, description overrides, and stored skill guide if available). Use list_plugins first to see which plugins are active, then call get_plugin_details(name) to load the schema for a specific plugin on demand.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-plugin-details.md
What get_plugin_details does on Meridian
AI agents call get_plugin_details 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Plugin name as returned by list_plugins (e.g. 'filesystem', 'code-intel', 'code-extractor'). |
Parameters from the server's own tool schema.
Why get_plugin_details is rated Low
This tool performs a read-only lookup operation to fetch plugin schema information. The explicit '[MAINTENANCE]' tag and 'Read-only' designation confirm it has no side effects. The severity is low because accessing plugin metadata poses minimal risk even if misused by an agent—it merely exposes schema information already discoverable via list_plugins.
From the tool's definition Described as 'Read-only' and retrieves 'Full schema for one named plugin' and 'tool definitions, description overrides, and stored skill guide'. No modification, deletion, or execution occurs; it queries and returns metadata.
Attacks that exploit this kind of access
The rule that runs get_plugin_details 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 get_plugin_details, this is the rule to start with:
get_plugin_details 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 get_plugin_details call is checked against it from then on.
Questions about get_plugin_details
[MAINTENANCE] Read-only: Full schema for one named plugin (all tool definitions, description overrides, and stored skill guide if available). Use list_plugins first to see which plugins are active, then call get_plugin_details(name) to load the schema for a specific plugin on demand. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_plugin_details accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for get_plugin_details: 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.
get_plugin_details 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 get_plugin_details 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 get_plugin_details. 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.
get_plugin_details 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