Comprehensive codebase analysis that generates rich project documentation and context files. Automatically discovers existing features when enabled in configuration.
AI agents call speclinter_analyze_codebase to retrieve information from SpecLinter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs codebase introspection and documentation generation—classic Read operations. It analyzes and extracts information from existing code without side effects. While it 'discovers existing features', this is passive analysis, not active modification. The tool has no capacity to execute code, modify files, delete data, or trigger external operations.
From the tool's definition The tool description states it 'generates rich project documentation and context files' and 'automatically discovers existing features'. These are analytical and discovery operations with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access speclinter_analyze_codebase gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SpecLinter MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for speclinter_analyze_codebase:
{
"version": "1",
"default": "deny",
"tools": {
"speclinter_analyze_codebase": {}
}
}speclinter_analyze_codebase is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Comprehensive codebase analysis that generates rich project documentation and context files. Automatically discovers existing features when enabled in configuration. It is categorised as a Read tool in the SpecLinter MCP MCP Server, which means it retrieves data without modifying state.
Register the SpecLinter MCP server in PolicyLayer and add a rule for speclinter_analyze_codebase: 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 SpecLinter MCP. Nothing to install.
speclinter_analyze_codebase 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 speclinter_analyze_codebase 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 speclinter_analyze_codebase. 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.
speclinter_analyze_codebase is provided by the SpecLinter MCP server (orangebread/speclinter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 SpecLinter MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 SpecLinter MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.