Runtime profile for a symbol or route: call count, latency percentiles (p50/p95/p99), error rate, calls per hour. Requires OTLP trace ingestion. Read-only, queries external runtime data. Use for performance analysis of specific endpoints. Returns JSON: { symbol_id, callCount, latency: { p50, p95,...
AI agents call get_runtime_profile 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.
This tool purely queries observability data (OTLP traces) and returns JSON performance statistics. It has no side effects, cannot modify code or systems, and poses no destruction or financial risk. The read-only designation and retrieval-only function clearly place it in the Read category.
From the tool's definition 'Read-only, queries external runtime data' and 'Runtime profile for a symbol or route: call count, latency percentiles (p50/p95/p99), error rate, calls per hour.' The tool retrieves performance metrics without modifying state.
Documented attack patterns abuse exactly the kind of access get_runtime_profile 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 get_runtime_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_runtime_profile": {}
}
}get_runtime_profile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Runtime profile for a symbol or route: call count, latency percentiles (p50/p95/p99), error rate, calls per hour. Requires OTLP trace ingestion. Read-only, queries external runtime data. Use for performance analysis of specific endpoints. Returns JSON: { symbol_id, callCount, latency: { p50, p95, p99 }, errorRate, callsPerHour }. 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_runtime_profile: 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_runtime_profile 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_runtime_profile 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_runtime_profile. 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_runtime_profile 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.
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.