AI agents call wordpress_get_reusable_block 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 retrieves reusable block content from WordPress by ID. It performs a query operation with no side effects—it does not create, modify, delete, or execute anything. The data returned is markup content that already exists. This is a straightforward read/retrieval operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name contains 'get' and description states 'Get a synced pattern (reusable block) by ID including its block markup content.' The verb 'Get' and the action of retrieving/querying data without modification confirm this is a read operation.
Attacks that exploit this kind of access
Get a synced pattern (reusable block) by ID including its block markup content. 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_reusable_block: 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_reusable_block 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_reusable_block 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_reusable_block. 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_reusable_block 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 →