AI agents call wordpress_list_reusable_blocks 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 information about existing reusable blocks on a WordPress site. It performs no writes, deletions, executions, or financial operations—it only enumerates data. The blast radius of misuse is minimal; an attacker gains visibility into site content structure but cannot modify or delete anything.
From the tool's definition Tool name 'list' and description 'List synced patterns' indicate data retrieval with no modification capability. The verb 'list' is explicitly a Read operation per the schema.
Attacks that exploit this kind of access
List synced patterns (formerly reusable blocks) on the configured WordPress site. 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_list_reusable_blocks: 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_list_reusable_blocks 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_list_reusable_blocks 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_list_reusable_blocks. 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_list_reusable_blocks 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 →