Updates existing content of any type
AI agents use update_content to create or update resources in mcp-wordpress-instaWP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your mcp-wordpress-instaWP environment.
This tool creates or modifies data reversibly. It updates existing content without permanently deleting or destroying it, and does not involve financial transactions or code execution. The 'any type' scope and WordPress context (where content is central) warrant medium severity due to potential for broad impact, but it remains in the Write category as changes are reversible via version history or backups.
From the tool's definition Tool name is 'update_content' and description states it 'Updates existing content of any type', indicating modification of existing data.
Attacks that exploit this kind of access
Updates existing content of any type. It is categorised as a Write tool in the mcp-wordpress-instaWP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the mcp-wordpress-instaWP MCP server in PolicyLayer and add a rule for update_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 mcp-wordpress-instaWP. Nothing to install.
update_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 update_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 update_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.
update_content is provided by the mcp-wordpress-instaWP MCP server (pace8/mcp-wordpress). 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 →