Retrieve all categories from the WordPress site with their IDs, names, slugs, and post counts.
AI agents call get_wordpress_categories to retrieve information from WordPress AI Content System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about WordPress categories (IDs, names, slugs, post counts) without creating, modifying, or deleting any content. It is a pure read operation with no side effects and minimal blast radius if misused by an AI agent. The returned data is already public within the WordPress site and poses no security risk.
From the tool's definition Tool name 'get_wordpress_categories' and description 'Retrieve all categories from the WordPress site' indicate a retrieval operation with no modifications.
Attacks that exploit this kind of access
Retrieve all categories from the WordPress site with their IDs, names, slugs, and post counts. It is categorised as a Read tool in the WordPress AI Content System MCP Server, which means it retrieves data without modifying state.
Register the WordPress AI Content System MCP server in PolicyLayer and add a rule for get_wordpress_categories: 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 AI Content System. Nothing to install.
get_wordpress_categories 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 get_wordpress_categories 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 get_wordpress_categories. 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.
get_wordpress_categories is provided by the WordPress AI Content System MCP server (ssolis-ti/wordpress_content_ai_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 →