CRITICAL: Call this BEFORE editing any file. Shows files that historically change together. If file A is coupled with file B, editing A without B will likely cause a bug. Hidden couplings (no import between files) are especially dangerous.
AI agents call get_change_coupling to retrieve information from Codecortex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only analysis tool that queries structural and historical information about a codebase. It provides guidance to prevent bugs but does not execute, modify, or delete anything. The word 'CRITICAL' refers to its necessity in the development workflow, not to the risk category.
From the tool's definition Tool retrieves and displays historical change coupling data about files ('shows files that historically change together'). No modification, deletion, or code execution occurs.
Documented attack patterns abuse exactly the kind of access get_change_coupling gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codecortex, and nothing reaches the server without passing your rules. This is the rule we recommend for get_change_coupling:
{
"version": "1",
"default": "deny",
"tools": {
"get_change_coupling": {}
}
}get_change_coupling 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.
CRITICAL: Call this BEFORE editing any file. Shows files that historically change together. If file A is coupled with file B, editing A without B will likely cause a bug. Hidden couplings (no import between files) are especially dangerous. It is categorised as a Read tool in the Codecortex MCP Server, which means it retrieves data without modifying state.
Register the Codecortex MCP server in PolicyLayer and add a rule for get_change_coupling: 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 Codecortex. Nothing to install.
get_change_coupling 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_change_coupling 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_change_coupling. 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_change_coupling is provided by the Codecortex MCP server (rushikeshmore/codecortex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Codecortex, 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.
5 Codecortex tools catalogued and risk-classified — across an index of 43,000+ MCP servers.