analyze_perf

Per-tool latency telemetry: p50/p95/max, count, error_rate. Default reads the current session ring;

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/analyze-perf.md

WHAT IT DOES

What analyze_perf does on Trace

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

This tool queries performance telemetry and latency statistics, which are read-only operations that retrieve existing telemetry data without modifying, executing code, or causing destructive effects. The 'Default reads' language confirms it is a read operation. Misuse poses minimal risk as it only exposes performance metrics.

From the tool's definition The tool description states it 'reads the current session ring' and retrieves telemetry metrics (p50/p95/max latency, count, error_rate)—purely observational data with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

analyze_perf Allowed

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

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

FAQ

Questions about analyze_perf

What does the analyze_perf tool do? +

Per-tool latency telemetry: p50/p95/max, count, error_rate. Default reads the current session ring;. 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 analyze_perf? +

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

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

Can I rate-limit analyze_perf? +

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

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

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