list_traces
List recent request traces for a DenkOps project (name, status, duration, span count).
This record as markdown: /tools/denkopsai-mcp/list-traces.md
What list_traces does on Denkopsai
AI agents call list_traces 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 |
|---|---|---|---|
project_id | string | Yes |
Parameters from the server's own tool schema.
Why list_traces is rated Low
This tool retrieves and displays historical trace information (name, status, duration, span count) for monitoring and observability purposes. It performs a read-only query operation with no side effects, making data retrieval its sole function. The blast radius is minimal—misuse would only expose trace metadata without enabling unauthorized modifications or resource consumption.
From the tool's definition Tool name 'list_traces' and description 'List recent request traces' indicate retrieval/querying of trace data with no modification or destructive operations.
Attacks that exploit this kind of access
The rule that runs list_traces 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 list_traces, this is the rule to start with:
list_traces is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Denkopsai, apply this rule, and every list_traces call is checked against it from then on.
Questions about list_traces
List recent request traces for a DenkOps project (name, status, duration, span count). It is categorised as a Read tool in the Denkopsai MCP Server, which means it retrieves data without modifying state.
list_traces accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for list_traces: 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.
list_traces 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 list_traces 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 list_traces. 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.
list_traces 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.
More on Denkopsai, and thousands of servers like it.
This server
Across the catalogue