Get actionable codebase health signals from the latest index. Returns the highest-risk files and their reasons, or a single file when requested.
AI agents call get_codebase_health to retrieve information from Codebase Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_codebase_health is a read-only tool that retrieves and reports analysis from an index. It queries codebase metadata to surface health metrics and risk information but does not execute code, modify files, delete data, or trigger external operations. The highest-risk category applicable is Read.
From the tool's definition Tool returns codebase health signals and analysis; described as providing 'visibility' and 'returns' data about files and risks without any modify, delete, execute, or financial operations.
Documented attack patterns abuse exactly the kind of access get_codebase_health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codebase Context, and nothing reaches the server without passing your rules. This is the rule we recommend for get_codebase_health:
{
"version": "1",
"default": "deny",
"tools": {
"get_codebase_health": {}
}
}get_codebase_health 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.
Get actionable codebase health signals from the latest index. Returns the highest-risk files and their reasons, or a single file when requested. It is categorised as a Read tool in the Codebase Context MCP Server, which means it retrieves data without modifying state.
Register the Codebase Context MCP server in PolicyLayer and add a rule for get_codebase_health: 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 Codebase Context. Nothing to install.
get_codebase_health 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 get_codebase_health 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 get_codebase_health. 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.
get_codebase_health is provided by the Codebase Context MCP server (patricksys/codebase-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Codebase Context tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Codebase Context tools catalogued and risk-classified — across an index of 42,500+ MCP servers.