get_tech_debt

Per-module tech debt score (A–F grade) combining: complexity, coupling instability, test coverage gaps, and git churn. Includes actionable recommendations. Use for architecture review and prioritizing cleanup. Read-only. Returns JSON: { modules: [{ module, grade, score, factors, recommendations }...

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-tech-debt.md

WHAT IT DOES

What get_tech_debt does on Trace

AI agents call get_tech_debt 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_tech_debt is rated Low

This tool retrieves and queries computed metrics (tech debt scores, complexity, coupling, test coverage) about source code modules. It performs analysis and returns structured data without modifying code, executing commands, or triggering side effects. The 'read-only' designation confirms no state changes occur.

From the tool's definition Tool description explicitly states 'Read-only' and 'Returns JSON' with analytics data (tech debt scores, grades, factors, recommendations). No write, execute, delete, or financial operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_tech_debt Allowed

get_tech_debt 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_tech_debt": {}
  }
}

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

FAQ

Questions about get_tech_debt

What does the get_tech_debt tool do? +

How do I enforce a policy on get_tech_debt? +

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

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

Can I rate-limit get_tech_debt? +

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

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

get_tech_debt 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_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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