wordpress_get_block_editor_settings
AI agents call wordpress_get_block_editor_settings 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.
This tool appears to fetch or query block editor settings (WordPress's native editor configuration). The 'get_' prefix denotes read-only semantics. Without evidence of side effects, state modification, or command execution, it falls under Read. Severity is low because retrieving settings poses minimal risk even if exposed to an AI agent—the worst case involves disclosing non-sensitive editor preferences.
From the tool's definition Tool name 'wordpress_get_block_editor_settings' uses the verb 'get', indicating data retrieval. The description is empty, preventing full assessment, but the naming convention and context on a WordPress management server strongly suggest this retrieves…
Documented attack patterns abuse exactly the kind of access wordpress_get_block_editor_settings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wordpress_get_block_editor_settings:
{
"version": "1",
"default": "deny",
"tools": {
"wordpress_get_block_editor_settings": {}
}
}wordpress_get_block_editor_settings 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.
wordpress_get_block_editor_settings. 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_editor_settings: 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_editor_settings 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_editor_settings 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_editor_settings. 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_editor_settings is provided by the WordPress MCP Server MCP server (raheesahmed/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 190 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
190 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.