get_startup_context_audit
What every session pays before your first message, what it costs, and what went unused: source decomposition, cache-rebuild prices, and removals proven unused — never merely big.
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-startup-context-audit.md
What get_startup_context_audit does on Trace
AI agents call get_startup_context_audit 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.
Why get_startup_context_audit is rated Low
Tool queries session startup costs and resource metrics; read-only introspection with no modifications.
From the tool's definition audit, decomposition, costs, unused — retrieves analysis metrics without side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_startup_context_audit 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_startup_context_audit, this is the rule to start with:
get_startup_context_audit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_startup_context_audit call is checked against it from then on.
Questions about get_startup_context_audit
What every session pays before your first message, what it costs, and what went unused: source decomposition, cache-rebuild prices, and removals proven unused — never merely big. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for get_startup_context_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.
get_startup_context_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_startup_context_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.
Set action: deny in the PolicyLayer policy for get_startup_context_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.
get_startup_context_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.
More on Trace, and thousands of servers like it.
This server
Across the catalogue