AI agents call wordpress_get_post_type to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves WordPress post type information without modifying data. Post types are structural metadata (post, page, custom post types), and querying them has no side effects. Even if misused by an AI agent, retrieving post type data poses minimal risk. The low severity reflects that this is basic informational access with no destructive, financial, or system-altering consequences.
From the tool's definition Tool name 'wordpress_get_post_type' indicates retrieval of post type metadata or configuration. The 'get' prefix and absence of mutation language strongly suggest a read-only operation.
Documented attack patterns abuse exactly the kind of access wordpress_get_post_type 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_get_post_type:
{
"version": "1",
"default": "deny",
"tools": {
"wordpress_get_post_type": {}
}
}wordpress_get_post_type is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
wordpress_get_post_type. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_get_post_type: 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_get_post_type 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 wordpress_get_post_type 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_get_post_type. 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_get_post_type 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.