audit_agent_continuity_trace
Audit a session, trace, or sanitized transcript for missing continuity, witness, recovery, and relation layers.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/audit-agent-continuity-trace.md
What audit_agent_continuity_trace does on Delx Protocol — Agent Recovery & Continuity
AI agents call audit_agent_continuity_trace to retrieve information from Delx Protocol — Agent Recovery & Continuity 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 | string | — | Optional compact trace of tools, failures, or handoff state. |
agent_id | string | — | Optional stable agent id. |
last_tool | string | — | Optional last Delx tool called. |
session_id | string | — | Optional session id to audit. |
transcript | string | — | Optional sanitized transcript excerpt. |
current_goal | string | — | What the agent is trying to accomplish. |
Parameters from the server's own tool schema.
Why audit_agent_continuity_trace is rated Low
Even though audit_agent_continuity_trace only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs audit_agent_continuity_trace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audit_agent_continuity_trace, this is the rule to start with:
audit_agent_continuity_trace 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 Delx Protocol — Agent Recovery & Continuity, apply this rule, and every audit_agent_continuity_trace call is checked against it from then on.
Questions about audit_agent_continuity_trace
Audit a session, trace, or sanitized transcript for missing continuity, witness, recovery, and relation layers. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
audit_agent_continuity_trace accepts 6 parameters: trace, agent_id, last_tool, session_id, transcript, current_goal. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for audit_agent_continuity_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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
audit_agent_continuity_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 audit_agent_continuity_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 audit_agent_continuity_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.
audit_agent_continuity_trace is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue