audit_config

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/audit-config.md

WHAT IT DOES

What audit_config does on Trace

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

The tool performs a read-only scan of configuration files and returns analysis results. It does not modify, delete, or execute anything. Severity is medium because it reads potentially sensitive AI agent configuration files (CLAUDE.md, AGENTS.md, .cursorrules) which could reveal system prompts, tool surfaces, and internal agent rules if misused.

From the tool's definition 'Read-only. Returns JSON: { issues: [...], total }' and 'Scan AI agent config files ... for stale references, dead paths, token bloat, and drift'

Attacks that exploit this kind of access

RECOMMENDED RULE

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

audit_config Allowed

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

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

FAQ

Questions about audit_config

What does the audit_config tool do? +

Scan AI agent config files (CLAUDE.md, AGENTS.md, .cursorrules, etc.) for stale references, dead paths, token bloat, and (when include_drift is set) drift between agent rules and the live MCP tool / skill / command surface. Read-only. Returns JSON: { issues: [{ file, line, category, issue, severity, fix? }], 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 audit_config? +

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

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

Can I rate-limit audit_config? +

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

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

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