Get all spans in a distributed trace as a hierarchical tree. Use this tool to: - Debug a specific request end-to-end - See the full call chain from HTTP request to database queries - Understand timing and dependencies between spans - Identify bottlenecks in a request First use query_spans to find...
AI agents call get_trace to retrieve information from Tusk Drift MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays hierarchical trace data for debugging and analysis purposes. It queries existing captured traffic data without creating, modifying, executing, deleting, or moving any resources. The blast radius of misuse is minimal — an agent could access trace data it shouldn't, but cannot alter application state or trigger operations.
From the tool's definition Tool description states 'Get all spans in a distributed trace' and use cases include 'Debug a specific request end-to-end', 'See the full call chain', 'Understand timing', and 'Identify bottlenecks' — all read-only analysis operations with no modification or…
Documented attack patterns abuse exactly the kind of access get_trace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tusk Drift MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_trace:
{
"version": "1",
"default": "deny",
"tools": {
"get_trace": {}
}
}get_trace 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.
Get all spans in a distributed trace as a hierarchical tree. Use this tool to: - Debug a specific request end-to-end - See the full call chain from HTTP request to database queries - Understand timing and dependencies between spans - Identify bottlenecks in a request First use query_spans to find spans, then use the traceId to get the full trace. It is categorised as a Read tool in the Tusk Drift MCP MCP Server, which means it retrieves data without modifying state.
Register the Tusk Drift MCP server in PolicyLayer and add a rule for get_trace: 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 Tusk Drift MCP. Nothing to install.
get_trace 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_trace 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_trace. 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_trace is provided by the Tusk Drift MCP server (use-tusk/drift-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tusk Drift MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Tusk Drift MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.