seo_bulk_update_posts_seo
Bulk update SEO meta of up to 100 posts. Each item is { id, ...fields } with the same fields as seo_update_post_seo (null deletes a field, omitted fields are kept). Returns { updated, errors: [{ index, id?, message }] }.
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/seo-bulk-update-posts-seo.md
What seo_bulk_update_posts_seo does on Wordpress
AI agents use seo_bulk_update_posts_seo 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 seo_bulk_update_posts_seo is rated Medium
Updates post metadata in bulk; changes are reversible and no data is permanently deleted.
From the tool's definition Bulk update SEO meta of up to 100 posts, modifies fields reversibly
Attacks that exploit this kind of access
The rule that runs seo_bulk_update_posts_seo 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 seo_bulk_update_posts_seo, this is the rule to start with:
seo_bulk_update_posts_seo 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 seo_bulk_update_posts_seo call is checked against it from then on.
Questions about seo_bulk_update_posts_seo
Bulk update SEO meta of up to 100 posts. Each item is { id, ...fields } with the same fields as seo_update_post_seo (null deletes a field, omitted fields are kept). Returns { updated, errors: [{ index, id?, message }] }. 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 seo_bulk_update_posts_seo: 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.
seo_bulk_update_posts_seo 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 seo_bulk_update_posts_seo 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 seo_bulk_update_posts_seo. 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.
seo_bulk_update_posts_seo 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