Get Gutenberg block development standards and best practices
AI agents call get_gutenberg_standards 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 or queries development standards and best practices documentation. It has no side effects, does not modify data, execute code, or trigger external operations. It is purely informational, similar to fetching API documentation or style guides.
From the tool's definition Tool name 'get_gutenberg_standards' and description 'Get Gutenberg block development standards and best practices' indicate retrieval of reference documentation without data modification or code execution.
Documented attack patterns abuse exactly the kind of access get_gutenberg_standards 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_gutenberg_standards:
{
"version": "1",
"default": "deny",
"tools": {
"get_gutenberg_standards": {}
}
}get_gutenberg_standards 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 Gutenberg block development standards 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_gutenberg_standards: 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_gutenberg_standards 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_gutenberg_standards 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_gutenberg_standards. 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_gutenberg_standards 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.