seo_list_posts_seo
List SEO meta of published posts, newest ID first: [{ id, title, url, seo, language?, translations? }].
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/seo-list-posts-seo.md
What seo_list_posts_seo does on Wordpress
AI agents call seo_list_posts_seo to retrieve information from Wordpress without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why seo_list_posts_seo is rated Low
Tool queries and returns existing SEO metadata from published posts with no modification or execution capability.
From the tool's definition List SEO meta of published posts; retrieves data without side effects
Attacks that exploit this kind of access
The rule that runs seo_list_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_list_posts_seo, this is the rule to start with:
seo_list_posts_seo is read-only, so it stays allowed. 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_list_posts_seo call is checked against it from then on.
Questions about seo_list_posts_seo
List SEO meta of published posts, newest ID first: [{ id, title, url, seo, language?, translations? }]. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Wordpress MCP server in PolicyLayer and add a rule for seo_list_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_list_posts_seo is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the seo_list_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_list_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_list_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