get_co_changes

Find files that frequently change together in git history (temporal coupling). Requires git. Use to discover hidden dependencies between files. For cross-module co-change anomalies use detect_drift instead. Read-only. Returns JSON: { file, coChanges: [{ file, confidence, count }] }.

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-co-changes.md

WHAT IT DOES

What get_co_changes does on Trace

AI agents call get_co_changes to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_co_changes is rated Low

This tool retrieves and analyzes historical metadata from git to identify temporal coupling patterns between files. It performs a query operation on existing git data with no capability to modify, delete, or execute code. The severity is low because reading git history poses minimal risk—an agent cannot misuse this to harm systems or data.

From the tool's definition The tool description explicitly states 'Read-only' and the functionality is 'Find files that frequently change together in git history'. It 'Returns JSON' with analysis data and has no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_co_changes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_co_changes, this is the rule to start with:

get_co_changes Allowed

get_co_changes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_co_changes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_co_changes call is checked against it from then on.

FAQ

Questions about get_co_changes

What does the get_co_changes tool do? +

How do I enforce a policy on get_co_changes? +

Register the Trace MCP server in PolicyLayer and add a rule for get_co_changes: 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 Trace. Nothing to install.

What risk level is get_co_changes? +

get_co_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_co_changes? +

Yes. Add a rate_limit block to the get_co_changes 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.

How do I block get_co_changes completely? +

Set action: deny in the PolicyLayer policy for get_co_changes. 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.

What MCP server provides get_co_changes? +

get_co_changes is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

review_changes on MCP Server PR Pilot →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →