New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_runtime_call_graph

Actual call graph from runtime traces (vs static analysis). Shows observed call paths with call counts and latency. Requires OTLP trace ingestion. Read-only, queries external runtime data. For static call graph use get_call_graph instead. Returns JSON: { root, calls: [{ symbol, count, latency }] }.

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/get-runtime-call-graph.md

What get_runtime_call_graph does on Trace

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

This tool performs data retrieval only—it queries existing runtime traces from an OTLP ingestion system and returns call graph data in JSON format. There are no side effects, modifications, deletions, code execution, or financial operations.

From the tool's definition The tool is described as 'Read-only, queries external runtime data' and 'shows observed call paths with call counts and latency.' It retrieves runtime trace information without modification.

Risk signalsAdmin/system-level operation

Questions about get_runtime_call_graph

What does the get_runtime_call_graph tool do? +

Actual call graph from runtime traces (vs static analysis). Shows observed call paths with call counts and latency. Requires OTLP trace ingestion. Read-only, queries external runtime data. For static call graph use get_call_graph instead. Returns JSON: { root, calls: [{ symbol, count, latency }] }. 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 get_runtime_call_graph? +

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

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

Can I rate-limit get_runtime_call_graph? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Trace's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.