AI agents use wordpress_update_term to create or update resources in WordPress MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.
WordPress terms (categories, tags, custom taxonomies) are data entities that can be modified. Updating a term is a write operation that modifies existing data reversibly. Without a detailed description, we cannot confirm if this could affect multiple sites or critical taxonomies, but term updates are generally lower-impact than theme/plugin activation or capability changes also present on this server.
From the tool's definition Tool name indicates updating a term (likely taxonomy terms like categories/tags in WordPress). With no description provided, confidence is reduced. The 'update' operation is inherently reversible, placing it in Write rather than Destructive.
Documented attack patterns abuse exactly the kind of access wordpress_update_term gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wordpress_update_term:
{
"version": "1",
"default": "deny",
"tools": {
"wordpress_update_term": {
"limits": [
{
"counter": "wordpress_update_term_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wordpress_update_term stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
wordpress_update_term. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_update_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 WordPress MCP Server. Nothing to install.
wordpress_update_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 wordpress_update_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 wordpress_update_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.
wordpress_update_term is provided by the WordPress MCP Server MCP server (raheesahmed/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 190 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
190 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.