get_coupling_trend

File coupling over git history: Ca/Ce/instability at past commits. Shows if a module is stabilizing or destabilizing. Requires git. Use to track module stability over time. For current coupling snapshot use get_coupling instead. Read-only. Returns JSON: { file, snapshots: [{ commit, date, ca, ce,...

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-coupling-trend.md

WHAT IT DOES

What get_coupling_trend does on Trace

AI agents call get_coupling_trend 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_coupling_trend is rated Low

This tool queries historical code coupling metrics from git history to analyze module stability trends. It performs no writes, deletes, executions of external code, or financial operations. It is a straightforward read operation that fetches metrics for analysis purposes. The explicit 'Read-only' designation confirms this classification.

From the tool's definition Tool description explicitly states 'Read-only' and 'Returns JSON' with historical coupling metrics (ca, ce, instability). It retrieves and queries git history and code metrics without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_coupling_trend 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_coupling_trend, this is the rule to start with:

get_coupling_trend Allowed

get_coupling_trend 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_coupling_trend": {}
  }
}

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_coupling_trend call is checked against it from then on.

FAQ

Questions about get_coupling_trend

What does the get_coupling_trend tool do? +

How do I enforce a policy on get_coupling_trend? +

Register the Trace MCP server in PolicyLayer and add a rule for get_coupling_trend: 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_coupling_trend? +

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

Can I rate-limit get_coupling_trend? +

Yes. Add a rate_limit block to the get_coupling_trend 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_coupling_trend completely? +

Set action: deny in the PolicyLayer policy for get_coupling_trend. 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_coupling_trend? +

get_coupling_trend 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

get_regional_trend on 08-AI-Business-Agent →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 →