Generate complete Gutenberg block code including block.json, PHP registration, and React components
AI agents use generate_gutenberg_block to create or update resources in BOIM WordPress Stack MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BOIM WordPress Stack MCP environment.
This tool creates new code files and configurations for WordPress Gutenberg blocks. While it does not directly modify an existing WordPress installation or execute code against a live system, it produces write artifacts that developers would integrate into their projects.
From the tool's definition Tool generates and produces code artifacts (block.json, PHP registration, React components) that would be written to files or systems. Description states 'Generate complete Gutenberg block code' - a generative action producing new code content.
Documented attack patterns abuse exactly the kind of access generate_gutenberg_block gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BOIM WordPress Stack MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_gutenberg_block:
{
"version": "1",
"default": "deny",
"tools": {
"generate_gutenberg_block": {
"limits": [
{
"counter": "generate_gutenberg_block_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} generate_gutenberg_block stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate complete Gutenberg block code including block.json, PHP registration, and React components. It is categorised as a Write tool in the BOIM WordPress Stack MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BOIM WordPress Stack MCP server in PolicyLayer and add a rule for generate_gutenberg_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 BOIM WordPress Stack MCP. Nothing to install.
generate_gutenberg_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 generate_gutenberg_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 generate_gutenberg_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.
generate_gutenberg_block is provided by the BOIM WordPress Stack MCP server (jtruax/boim-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BOIM WordPress Stack MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 BOIM WordPress Stack MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.