Creates a plugin from the WordPress.org repository
AI agents use create_plugin to create or update resources in FluentCommunity Manager — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FluentCommunity Manager environment.
This tool creates (installs) a WordPress plugin, which is a Write operation as it adds new functionality to the WordPress installation. However, the severity is elevated to 'high' rather than 'medium' because plugin installation can introduce arbitrary code execution risks, supply chain vulnerabilities, and potentially compromise site security depending on plugin source and permissions.
From the tool's definition Tool name: 'create_plugin'; description: 'Creates a plugin from the WordPress.org repository'. The verb 'creates' indicates a Write action that adds new data/functionality to the system.
Attacks that exploit this kind of access
Creates a plugin from the WordPress.org repository. It is categorised as a Write tool in the FluentCommunity Manager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for create_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.
create_plugin is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →