AI agents use wordpress_create_reusable_block to create or update resources in ItchWPMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ItchWPMCP environment.
Creating a reusable block is a write operation that stores new content in WordPress, but it is not destructive (it can be deleted later), not financial, and not execute/code-running.
From the tool's definition Tool description states 'Create a synced pattern (reusable block)' — the verb 'Create' combined with 'synced pattern' indicates the tool creates new WordPress content that is stored and reusable across posts/pages. This is a reversible write operation.
Attacks that exploit this kind of access
Create a synced pattern (reusable block) with block markup content. It is categorised as a Write tool in the ItchWPMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ItchWP MCP server in PolicyLayer and add a rule for wordpress_create_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_create_reusable_block is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wordpress_create_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_create_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_create_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 →