mcp_update_term
Update a term in any taxonomy. Only the given fields change.
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/mcp-update-term.md
What mcp_update_term does on Wordpress
AI agents use mcp_update_term to create or update resources in Wordpress, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wordpress environment.
Why mcp_update_term is rated Medium
Modifies taxonomy terms reversibly; high-value data but not destructive or financial.
From the tool's definition Update a term in any taxonomy. Only the given fields change.
Attacks that exploit this kind of access
The rule that runs mcp_update_term safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_update_term, this is the rule to start with:
mcp_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every mcp_update_term call is checked against it from then on.
Questions about mcp_update_term
Update a term in any taxonomy. Only the given fields change. It is categorised as a Write tool in the Wordpress MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wordpress MCP server in PolicyLayer and add a rule for mcp_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. Nothing to install.
mcp_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 mcp_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 mcp_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.
mcp_update_term is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
This server
Across the catalogue