Analyzes codebase and generates three foundational analysis documents: product.md, tech.md, and structure.md in .spec/steering/ directory. These documents provide comprehensive analysis of the product features, technology stack, and project structure. Checks if files already exist and skips gener...
AI agents use generate-codebase-analysis to create or update resources in Spec MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spec MCP Server environment.
The tool creates or modifies documentation files within the codebase directory structure. While the action is reversible (files can be deleted or re-edited), it does modify the filesystem state. This is Write-category behavior rather than Read (which would only retrieve information) or Execute (which would run arbitrary code).
From the tool's definition Tool description states it 'generates three foundational analysis documents: product.md, tech.md, and structure.md in .spec/steering/ directory' and 'Checks if files already exist and skips generation unless force_regenerate is true.' This directly indicates…
Attacks that exploit this kind of access
Analyzes codebase and generates three foundational analysis documents: product.md, tech.md, and structure.md in .spec/steering/ directory. These documents provide comprehensive analysis of the product features, technology stack, and project structure. Checks if files already exist and skips generation unless force_regenerate is true. It is categorised as a Write tool in the Spec MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spec MCP Server MCP server in PolicyLayer and add a rule for generate-codebase-analysis: 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 Spec MCP Server. Nothing to install.
generate-codebase-analysis is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate-codebase-analysis 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 generate-codebase-analysis. 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.
generate-codebase-analysis is provided by the Spec MCP Server MCP server (karol-f/spec-mcp). 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 →