Get GenerateBlocks development guide and best practices
AI agents call get_generateblocks_guide to retrieve information from BOIM WordPress Stack MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static documentation and best practices guides for GenerateBlocks development. It is a read-only operation that queries existing knowledge resources without creating, modifying, deleting, executing code, or causing side effects. The low severity reflects that misuse would only result in access to development documentation.
From the tool's definition Tool name 'get_generateblocks_guide' and description 'Get GenerateBlocks development guide and best practices' indicate retrieval of documentation/reference material with no data modification or command execution.
Documented attack patterns abuse exactly the kind of access get_generateblocks_guide 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 get_generateblocks_guide:
{
"version": "1",
"default": "deny",
"tools": {
"get_generateblocks_guide": {}
}
}get_generateblocks_guide is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get GenerateBlocks development guide and best practices. It is categorised as a Read tool in the BOIM WordPress Stack MCP MCP Server, which means it retrieves data without modifying state.
Register the BOIM WordPress Stack MCP server in PolicyLayer and add a rule for get_generateblocks_guide: 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.
get_generateblocks_guide 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 get_generateblocks_guide 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 get_generateblocks_guide. 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.
get_generateblocks_guide 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.