Low Risk

self_audit

Dead code & coverage audit: dead exports, untested public symbols, heritage debt. Use as a one-shot health check combining dead exports + untested symbols + heritage debt. For individual checks use get_dead_exports, get_untested_symbols, or get_dead_code separately. Read-only. Returns JSON: { dea...

How to control self_audit ↓

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

Low Risk

This tool analyzes source code to identify code quality metrics and dead code patterns, but does not create, modify, delete, or execute any code. It is a pure read-only analysis tool that returns structured data for inspection. No side effects or irreversible actions are possible.

From the tool's definition Tool description explicitly states 'Read-only' and performs auditing/analysis operations: 'Dead code & coverage audit', 'dead exports', 'untested public symbols', 'heritage debt'. Returns JSON data without modifying code.

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

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

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

self_audit 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 Trace — 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.

Go deeper

What does the self_audit tool do? +

Dead code & coverage audit: dead exports, untested public symbols, heritage debt. Use as a one-shot health check combining dead exports + untested symbols + heritage debt. For individual checks use get_dead_exports, get_untested_symbols, or get_dead_code separately. Read-only. Returns JSON: { deadExports, untestedSymbols, heritageDebt, summary }. 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 self_audit? +

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

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

Can I rate-limit self_audit? +

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

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

self_audit 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.

Enforce policy on every Trace tool call.

Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

178 Trace tools catalogued and risk-classified — across an index of 42,500+ 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.