Low Risk

find_tech_debt

Surface TODO/FIXME/HACK/OPTIMIZE markers stored in the graph during indexing. Returns symbols sorted by risk score (debt_count × caller_count) so agents tackle the highest-impact debt first.

How to control find_tech_debt ↓

What find_tech_debt does on GraphHub

AI agents call find_tech_debt to retrieve information from GraphHub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why find_tech_debt needs a policy

This is a pure read operation that queries a pre-built graph to retrieve technical debt markers and metadata (debt_count, caller_count). There are no side effects: no data is modified, deleted, executed, or financed. The tool simply exposes static analysis results for informational purposes to help prioritize code review work.

From the tool's definition Tool 'find_tech_debt' surfaces and returns TODO/FIXME/HACK/OPTIMIZE markers from an indexed knowledge graph. It retrieves and sorts existing data with no modification, creation, deletion, or external execution.

Documented attack patterns abuse exactly the kind of access find_tech_debt gives an agent:

How to control find_tech_debt

PolicyLayer is an MCP gateway — it sits between your AI agents and GraphHub, and nothing reaches the server without passing your rules. This is the rule we recommend for find_tech_debt:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_tech_debt": {}
  }
}

find_tech_debt is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GraphHub — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about find_tech_debt

What does the find_tech_debt tool do? +

Surface TODO/FIXME/HACK/OPTIMIZE markers stored in the graph during indexing. Returns symbols sorted by risk score (debt_count × caller_count) so agents tackle the highest-impact debt first. It is categorised as a Read tool in the GraphHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_tech_debt? +

Register the GraphHub MCP server in PolicyLayer and add a rule for find_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 GraphHub. Nothing to install.

What risk level is find_tech_debt? +

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

Can I rate-limit find_tech_debt? +

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

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

find_tech_debt is provided by the GraphHub MCP server (slnquangtran/graph-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GraphHub tool call.

Start from GraphHub, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

32 GraphHub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.