wordpress_set_featured_image
AI agents use wordpress_set_featured_image 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.
Setting a featured image modifies post data reversibly—the image can be changed or removed. This is a Write operation (creates or modifies data reversibly) rather than Read (no side effects) or more severe categories. Severity is medium because an AI agent could modify many posts' featured images, affecting site presentation, but changes are easily undone.
From the tool's definition Tool name 'wordpress_set_featured_image' indicates modification of post metadata; context of WordPress MCP Server with 190+ management tools confirms this is a content modification operation.
Attacks that exploit this kind of access
wordpress_set_featured_image. 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_set_featured_image: 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_set_featured_image 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_set_featured_image 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_set_featured_image. 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_set_featured_image is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/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 →