Assigns taxonomy terms to content of any type
AI agents use assign_terms_to_content 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.
Assigning terms to content is a Write operation because it modifies content metadata and taxonomy relationships. It is not Destructive because term assignment is reversible—terms can be reassigned or removed without data loss.
From the tool's definition The tool "assigns taxonomy terms to content of any type" modifies existing content by adding or updating taxonomy classifications. This is a reversible data modification operation (terms can be reassigned or removed).
Attacks that exploit this kind of access
Assigns taxonomy terms to content of any type. 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 assign_terms_to_content: 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.
assign_terms_to_content 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 assign_terms_to_content 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 assign_terms_to_content. 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.
assign_terms_to_content 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 →