wordpress_get_block_patterns
AI agents call wordpress_get_block_patterns to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix strongly suggests a read-only operation that queries or retrieves block pattern data. Even though the description is empty, reducing confidence slightly, the naming convention is a reliable indicator. Retrieving block patterns has no side effects and minimal blast radius if misused by an AI agent—it would only expose information already accessible in WordPress.
From the tool's definition Tool name 'wordpress_get_block_patterns' uses the verb 'get', indicating data retrieval. The tool appears to fetch block patterns (reusable content blocks) from WordPress without modifying them.
Attacks that exploit this kind of access
wordpress_get_block_patterns. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_get_block_patterns: 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 WordPress MCP Server. Nothing to install.
wordpress_get_block_patterns 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 wordpress_get_block_patterns 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_get_block_patterns. 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_get_block_patterns is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
wordpress_get_block_patterns is one line of WordPress MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →