// SCAN REPORT

BOIM WordPress Stack MCP

16 tools. 12 can modify or destroy data without limits.

12 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

12 can modify or destroy data

4 read-only

16 tools total

Community server · catalogue entry verified 12/06/2026

How to control BOIM WordPress Stack MCP ↓

TOOL MAP

What BOIM WordPress Stack MCP exposes to your agents

Read (4) Write / Execute (12) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous BOIM WordPress Stack MCP tools

Write · Medium format_for_wpcodebox This tool modifies or transforms code into a specific format for storage in WPCodebox. Write · Medium format_wpcodebox_snippet This tool creates new code snippets (Write category) rather than merely retrieving or viewing them. Write · Medium generate_block_pattern This tool creates new Gutenberg block patterns, which are reusable content templates stored in WordPress. Write · Medium generate_block_variation This tool creates or modifies block variation definitions in a WordPress/Gutenberg context.

12 of BOIM WordPress Stack MCP's 16 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control BOIM WordPress Stack MCP

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. These are the rules we recommend:

Rate limit write operations

{
  "format_for_wpcodebox": {
    "limits": [
      {
        "counter": "format_for_wpcodebox_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_generateblocks_guide": {
    "limits": [
      {
        "counter": "get_generateblocks_guide_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register BOIM WordPress Stack MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON BOIM WORDPRESS STACK →

Free to start. No card required.

FULL CATALOGUE

All 16 BOIM WordPress Stack MCP tools

WRITE 12 tools

Write format_for_wpcodebox Format any generated code for WPCodebox snippet structure Write format_wpcodebox_snippet Format a code snippet for WPCodebox plugin with proper structure and metadata Write generate_block_pattern Generate a Gutenberg block pattern Write generate_block_variation Generate a Gutenberg block variation Write generate_gb_block Generate GenerateBlocks-compatible block code Write generate_gb_styles Generate GenerateBlocks-specific SCSS (compile to CSS for production) Write generate_gb_template Generate GenerateBlocks template code Write generate_gutenberg_block Generate complete Gutenberg block code including block.json, PHP registration, and React components Write generate_hook Generate WordPress action or filter hook code Write generate_php_function Generate WordPress PHP function following coding standards Write generate_rest_endpoint Generate WordPress REST API endpoint Write generate_shortcode Generate WordPress shortcode implementation

READ 4 tools

Read get_generateblocks_guide Get GenerateBlocks development guide and best practices Read get_gutenberg_standards Get Gutenberg block development standards and best practices Read get_wpcodebox_guidelines Get WPCodebox usage guidelines and best practices Read validate_wpcodebox_snippet Validate a snippet structure against WPCodebox requirements

FAQ

Questions about BOIM WordPress Stack MCP

How do I prevent bulk modifications through BOIM WordPress Stack MCP? +

The BOIM WordPress Stack MCP server has 12 write tools including format_for_wpcodebox, format_wpcodebox_snippet, generate_block_pattern. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach BOIM WordPress Stack MCP.

How many tools does the BOIM WordPress Stack MCP server expose? +

16 tools across 2 categories: Read, Write. 4 are read-only. 12 can modify, create, or delete data.

How do I enforce a policy on BOIM WordPress Stack MCP? +

Register the BOIM WordPress Stack MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every BOIM WordPress Stack MCP tool call.

Deterministic rules across all 16 BOIM WordPress Stack MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BOIM WORDPRESS STACK →

Free to start. No card required.

16 BOIM WordPress Stack MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.