a11y_check_page_structure
Prüft die Accessibility-Struktur einer Seite (Heading-Hierarchie, Landmarks, etc.)
This record as markdown: /tools/c-sakel-wp-mcp-server/a11y-check-page-structure.md
What a11y_check_page_structure does on WordPress MCP Server
AI agents call a11y_check_page_structure to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why a11y_check_page_structure is rated Low
The tool performs accessibility analysis and validation of existing page structure. It retrieves and analyzes structural information (headings, landmarks) to generate reports, with no side effects or modifications to the WordPress site. This is a read-only diagnostic operation, similar to sibling tools like a11y_check_color_contrast and a11y_generate_report which are clearly Read category.
From the tool's definition Tool name contains 'a11y_check' and description states 'Prüft die Accessibility-Struktur' (checks the accessibility structure).
Attacks that exploit this kind of access
The rule that runs a11y_check_page_structure safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For a11y_check_page_structure, this is the rule to start with:
a11y_check_page_structure is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every a11y_check_page_structure call is checked against it from then on.
Questions about a11y_check_page_structure
Prüft die Accessibility-Struktur einer Seite (Heading-Hierarchie, Landmarks, etc.). 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 a11y_check_page_structure: 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.
a11y_check_page_structure 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 a11y_check_page_structure 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 a11y_check_page_structure. 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.
a11y_check_page_structure is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WordPress MCP Server, and thousands of servers like it.
This server
Across the catalogue