React/Next.js kodunu erişilebilirlik (a11y) açısından analiz eder. Semantic HTML, heading hiyerarşisi, alt text, ARIA label, keyboard erişimi, form label, renk kontrastı ve daha fazlasını WCAG standartlarına göre denetler.
AI agents call check_accessibility to retrieve information from MCP Frontend Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static code analysis and accessibility compliance checking. It retrieves and examines properties of code without modifying, deleting, or executing anything. The inspection of semantic HTML, ARIA attributes, heading structures, and contrast ratios are all non-destructive reads. No side effects, reversible operations, code execution, data deletion, or financial transactions are possible.
From the tool's definition The tool name is 'check_accessibility' and the description states it 'analyzes' React/Next.js code for accessibility (a11y) compliance, 'audits' semantic HTML, heading hierarchy, alt text, ARIA labels, keyboard access, form labels, and color contrast against…
Attacks that exploit this kind of access
React/Next.js kodunu erişilebilirlik (a11y) açısından analiz eder. Semantic HTML, heading hiyerarşisi, alt text, ARIA label, keyboard erişimi, form label, renk kontrastı ve daha fazlasını WCAG standartlarına göre denetler. It is categorised as a Read tool in the MCP Frontend Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Frontend Analyzer MCP server in PolicyLayer and add a rule for check_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 MCP Frontend Analyzer. Nothing to install.
check_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 check_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 check_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.
check_accessibility is provided by the MCP Frontend Analyzer MCP server (samet-berkay-taskin/mcp-frontend-analyzer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →