Calculate package metrics (Afferent/Efferent Coupling, Instability, Abstractness, Distance)
AI agents call calculate_package_metrics to retrieve information from CodeRAG without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool computes and retrieves software metrics from the codebase graph without creating, modifying, or deleting any data. It is purely informational analysis, fitting the Read category. The low severity reflects that misuse would only expose analytical information about code structure without side effects to the system.
From the tool's definition The tool name 'calculate_package_metrics' and description specify calculation of metrics (Afferent/Efferent Coupling, Instability, Abstractness, Distance) with no modification verbs.
Documented attack patterns abuse exactly the kind of access calculate_package_metrics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeRAG, and nothing reaches the server without passing your rules. This is the rule we recommend for calculate_package_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"calculate_package_metrics": {}
}
}calculate_package_metrics 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.
Calculate package metrics (Afferent/Efferent Coupling, Instability, Abstractness, Distance). It is categorised as a Read tool in the CodeRAG MCP Server, which means it retrieves data without modifying state.
Register the CodeRAG MCP server in PolicyLayer and add a rule for calculate_package_metrics: 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 CodeRAG. Nothing to install.
calculate_package_metrics 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 calculate_package_metrics 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 calculate_package_metrics. 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.
calculate_package_metrics is provided by the CodeRAG MCP server (jonnoc/coderag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeRAG, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 CodeRAG tools catalogued and risk-classified — across an index of 43,000+ MCP servers.