Analyze a project directory and return structured data about the project along with a README template.
AI agents call analyze_project to retrieve information from README Generator MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes information from a project directory to generate documentation metadata. It has no side effects, does not execute code, and does not modify any data. It is a classic Read operation: querying project structure and returning analysis results.
From the tool's definition Tool 'analyze_project' performs analysis and returns structured data about a project directory. The description indicates it 'analyze[s]' and 'return[s]' information without modifying the project.
Attacks that exploit this kind of access
Analyze a project directory and return structured data about the project along with a README template. It is categorised as a Read tool in the README Generator MCP Server MCP Server, which means it retrieves data without modifying state.
Register the README Generator MCP Server 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 README Generator MCP Server. 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 README Generator MCP Server MCP server (jojoslice/readme-gen-mcp-server). 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 →