get_risk_hotspots

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-risk-hotspots.md

WHAT IT DOES

What get_risk_hotspots does on Trace

AI agents call get_risk_hotspots 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_risk_hotspots is rated Low

Tool queries code metrics and git history to identify risk areas without modifying or executing code.

From the tool's definition hotspots analysis, read-only, returns JSON, heuristic triage

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_risk_hotspots Allowed

get_risk_hotspots 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_risk_hotspots": {}
  }
}

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

FAQ

Questions about get_risk_hotspots

What does the get_risk_hotspots tool do? +

Code hotspots: files with both high complexity AND high git churn (Adam Tornhill methodology). Score = complexity × log(1 + commits). Heuristic triage, not validated (calibration notes in _methodology). Requires git. For per-file bug-risk triage use predict_bugs instead. Read-only. Returns JSON: { hotspots: [{ file, score, max_cyclomatic, commits, assessment, confidence_level }], total }. Supports. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_risk_hotspots? +

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

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

Can I rate-limit get_risk_hotspots? +

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

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

get_risk_hotspots 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

aiva_get_churn_risk on AIVA MCP Server →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 →