get_health_trends

Time-series health metrics for a file or module: bug score, complexity, coupling, churn over time. Populated by predict_bugs runs. Use to track if a module is improving or degrading. Read-only. Returns JSON: { dataPoints: [{ date, bugScore, complexity, coupling, churn }] }.

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-health-trends.md

WHAT IT DOES

What get_health_trends does on Trace

AI agents call get_health_trends 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_health_trends is rated Low

This tool retrieves historical health metrics (bug score, complexity, coupling, churn) for code analysis purposes. It performs queries on existing data without modifying, creating, deleting, or executing any operations.

From the tool's definition Tool description explicitly states 'Read-only' and 'Returns JSON' with time-series metrics. The name 'get_health_trends' and operations described (track metrics over time) are purely retrieval operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_health_trends Allowed

get_health_trends 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_health_trends": {}
  }
}

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

FAQ

Questions about get_health_trends

What does the get_health_trends tool do? +

How do I enforce a policy on get_health_trends? +

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

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

Can I rate-limit get_health_trends? +

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

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

get_health_trends 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 →