detect_topic_tunnels

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/detect-topic-tunnels.md

WHAT IT DOES

What detect_topic_tunnels does on Trace

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

Tool analyzes and queries dependency relationships without modifying code or data.

From the tool's definition Cross-project links, read-only, returns JSON analysis

Attacks that exploit this kind of access

RECOMMENDED RULE

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

detect_topic_tunnels Allowed

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

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

FAQ

Questions about detect_topic_tunnels

What does the detect_topic_tunnels tool do? +

Cross-project topic tunnels: links between registered subprojects sharing canonical entities — manifest package names, top-level declared dependencies, and git contributors (bots filtered). Tunnel weight favors shared people/project names over common deps (noisy deps down-weighted). Use to discover hidden cross-repo coupling or seed cross-project search. Read-only. Returns JSON: { tunnels: [{ project_a, project_b, shared: [{ kind, canonical, display }], weight }], total }. 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 detect_topic_tunnels? +

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

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

Can I rate-limit detect_topic_tunnels? +

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

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

detect_topic_tunnels 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

The MCP Attack Database →

Guides

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