Retrieves plugin details
AI agents call get_plugin to retrieve information from FluentCommunity Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a plugin without creating, modifying, deleting, or executing anything. It is a straightforward query operation that falls squarely into the Read category with minimal risk potential. The low severity reflects that plugin metadata disclosure poses minimal security risk compared to other tool categories.
From the tool's definition Tool name 'get_plugin' and description 'Retrieves plugin details' indicate a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Retrieves plugin details. It is categorised as a Read tool in the FluentCommunity Manager MCP Server, which means it retrieves data without modifying state.
Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for get_plugin: 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 FluentCommunity Manager. Nothing to install.
get_plugin 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 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. 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 is provided by the FluentCommunity Manager MCP server (wplaunchify/fluent-community-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 →