React/Next.js component dosyasının kod kalitesini analiz eder. Satır sayısı, hook yoğunluğu, any kullanımı, console.log, import yapısı, SOLID prensipleri ve daha birçok metriği kontrol edip 0-100 arası skor verir.
AI agents call check_component_quality 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 quality assessment of React/Next.js components. It reads and evaluates code against quality metrics but produces no side effects on the codebase, system, or external services. The analysis is purely informational, making it a Read operation with low severity risk.
From the tool's definition Tool description states it 'analiz eder' (analyzes) component files and checks metrics like line count, hook density, TypeScript any usage, console.log statements, import structure, and SOLID principles, returning a 0-100 score.
Attacks that exploit this kind of access
React/Next.js component dosyasının kod kalitesini analiz eder. Satır sayısı, hook yoğunluğu, any kullanımı, console.log, import yapısı, SOLID prensipleri ve daha birçok metriği kontrol edip 0-100 arası skor verir. 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_component_quality: 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_component_quality 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_component_quality 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_component_quality. 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_component_quality 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 →