List recent agent execution traces, optionally filtered by agent name and time range. Returns trace IDs, timestamps, step counts, and success/failure status.
AI agents call trace_list to retrieve information from Scan Your Ai Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only queries on execution trace logs. It retrieves metadata about past agent runs (IDs, timestamps, counts, status) but does not modify, delete, or trigger any actions. The optional filtering parameters are query constraints, not operational arguments. There is no side effect beyond data retrieval, making it a straightforward Read classification.
From the tool's definition Tool 'trace_list' is described as listing recent agent execution traces with optional filters. It 'returns trace IDs, timestamps, step counts, and success/failure status' — purely retrieving and querying historical data without modifying, deleting, or…
Attacks that exploit this kind of access
List recent agent execution traces, optionally filtered by agent name and time range. Returns trace IDs, timestamps, step counts, and success/failure status. It is categorised as a Read tool in the Scan Your Ai Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Scan Your Ai Toolkit MCP server in PolicyLayer and add a rule for trace_list: 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 Scan Your Ai Toolkit. Nothing to install.
trace_list 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 trace_list 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 trace_list. 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.
trace_list is provided by the Scan Your Ai Toolkit MCP server (sakthivelchan89/scan_your_ai_toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →