get_trace

Get the spans of a single DenkOps request trace by project_id + trace_id.

SERVERDenkopsai SOURCE@denkopsai/mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/denkopsai-mcp/get-trace.md

WHAT IT DOES

What get_trace does on Denkopsai

AI agents call get_trace to retrieve information from Denkopsai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`trace_id`	string	Yes
`project_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_trace is rated Low

This tool retrieves observability/tracing data (spans from a request trace). It is a query operation that returns information about system behavior without altering state, executing code, deleting data, or moving money.

From the tool's definition Tool name 'get_trace' and description 'Get the spans of a single DenkOps request trace by project_id + trace_id' indicate retrieval of trace/monitoring data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_trace safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_trace, this is the rule to start with:

get_trace Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Denkopsai, apply this rule, and every get_trace call is checked against it from then on.

FAQ

Questions about get_trace

What does the get_trace tool do? +

Get the spans of a single DenkOps request trace by project_id + trace_id. It is categorised as a Read tool in the Denkopsai MCP Server, which means it retrieves data without modifying state.

What parameters does get_trace accept? +

get_trace accepts 2 parameters: trace_id, project_id. Required: trace_id, project_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_trace? +

Register the Denkopsai 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 Denkopsai. Nothing to install.

What risk level is get_trace? +

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

Can I rate-limit get_trace? +

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.

How do I block get_trace completely? +

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.

What MCP server provides get_trace? +

get_trace is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Denkopsai, and thousands of servers like it.

This server

All 28 Denkopsai tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →