scan_accessibility
Run built‑in accessibility scan on Elementor pages. Returns structured violations with severity, element type, location, description, and suggested fix.
This record as markdown: /tools/vamerli-elementify-mcp/scan-accessibility.md
What scan_accessibility does on Elementify MCP
AI agents call scan_accessibility to retrieve information from Elementify MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why scan_accessibility is rated Low
The scan_accessibility tool performs a passive analysis of Elementor pages to identify accessibility violations. It retrieves and returns structured data about accessibility issues but does not execute code, create/modify templates, delete content, or perform any financial operations. The tool's output (violations with severity, element type, location, description, and suggested fixes) is informational only.
From the tool's definition Tool description states it 'Run built‑in accessibility scan' and 'Returns structured violations' — this is a read-only operation that scans and reports accessibility issues without modifying, creating, or deleting any data.
Attacks that exploit this kind of access
The rule that runs scan_accessibility safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elementify MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_accessibility, this is the rule to start with:
scan_accessibility 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 Elementify MCP, apply this rule, and every scan_accessibility call is checked against it from then on.
Questions about scan_accessibility
Run built‑in accessibility scan on Elementor pages. Returns structured violations with severity, element type, location, description, and suggested fix. It is categorised as a Read tool in the Elementify MCP MCP Server, which means it retrieves data without modifying state.
Register the Elementify MCP server in PolicyLayer and add a rule for scan_accessibility: 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 Elementify MCP. Nothing to install.
scan_accessibility 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 scan_accessibility 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 scan_accessibility. 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.
scan_accessibility is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elementify, and thousands of servers like it.
This server
Across the catalogue