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 metadata but does not delete or destroy data, nor does it execute arbitrary code or trigger external operations. It is reversible—an image can be changed or unset. This qualifies as Write. Severity is medium because while the change affects published content visibility/presentation, it does not compromise site security or delete content.
From the tool's definition Tool name 'wordpress_set_featured_image' indicates modification of post metadata. Given the server manages WordPress sites with content management capabilities, this tool creates or modifies post-level data (featured image assignment) reversibly.
Documented attack patterns abuse exactly the kind of access wordpress_set_featured_image 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_set_featured_image:
{
"version": "1",
"default": "deny",
"tools": {
"wordpress_set_featured_image": {
"limits": [
{
"counter": "wordpress_set_featured_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wordpress_set_featured_image 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_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 (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.