Creates a new term in any taxonomy
AI agents use create_term 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.
Creating taxonomy terms modifies WordPress data structures reversibly—terms can be deleted or modified later. This is not a destructive action (which would be irreversible deletion), not an execute operation (no code execution), and not a read operation (creates rather than retrieves).
From the tool's definition Tool name 'create_term' and description 'Creates a new term in any taxonomy' indicate creating new data entries in WordPress taxonomies (categories, tags, custom taxonomies). This is a write operation that creates taxonomy terms.
Attacks that exploit this kind of access
Creates a new term in any taxonomy. 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_term: 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_term 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_term 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_term. 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_term 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 →