AI agents call wordpress_get_post_meta to retrieve information from ItchWPMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves post metadata through the WordPress REST API. It has no side effects, performs no modifications, and cannot create, delete, or execute operations. The 'keys' parameter merely filters the returned data. Reading post metadata poses minimal risk; the worst case is information disclosure of non-sensitive metadata already accessible through standard WordPress queries.
From the tool's definition Tool name contains 'get' and description states 'Get registered WordPress REST meta' — retrieves metadata without modification.
Attacks that exploit this kind of access
Get registered WordPress REST meta for a page or post. Use keys to limit the returned meta fields. It is categorised as a Read tool in the ItchWPMCP MCP Server, which means it retrieves data without modifying state.
Register the ItchWP MCP server in PolicyLayer and add a rule for wordpress_get_post_meta: 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 ItchWPMCP. Nothing to install.
wordpress_get_post_meta 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_meta 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_meta. 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_meta is provided by the ItchWP MCP server (manofsadness/itchwpmcp). 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 →