Analyze project files for FSD violations and naming conventions.
AI agents call analyze_project to retrieve information from Mcp React Frontend without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs static code analysis and validation, which is a non-destructive, side-effect-free retrieval and inspection activity. While it may report problems, it does not create, modify, delete, or execute any code or external operations. This is a classic Read category operation.
From the tool's definition Tool description states 'Analyze project files' — a read-only operation that examines code without modifying, deleting, or executing anything. It retrieves structural and naming information to report violations.
Attacks that exploit this kind of access
Analyze project files for FSD violations and naming conventions. It is categorised as a Read tool in the Mcp React Frontend MCP Server, which means it retrieves data without modifying state.
Register the Mcp React Frontend MCP server in PolicyLayer and add a rule for analyze_project: 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 React Frontend. Nothing to install.
analyze_project 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 analyze_project 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 analyze_project. 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.
analyze_project is provided by the Mcp React Frontend MCP server (kdf25/mcp-react-frontend). 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 →