dcl_audit_decode_deep
POST-ACTION Deep Forensic Audit ($0.50). Extended output with drift_context and full chain integrity verification.
This record as markdown: /tools/com-fronesislabs-dcl-trust-oracle/dcl-audit-decode-deep.md
What dcl_audit_decode_deep does on Dcl Trust Oracle
AI agents call dcl_audit_decode_deep to retrieve information from Dcl Trust Oracle 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 |
|---|---|---|---|
tx_hash | string | Yes | Transaction hash of the audit chain record to retrieve. |
Parameters from the server's own tool schema.
Why dcl_audit_decode_deep is rated Low
Inspects and reports on existing data integrity; no creation, modification, or deletion of records.
From the tool's definition Deep forensic audit, decode output, verification—no mutations
Attacks that exploit this kind of access
The rule that runs dcl_audit_decode_deep safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dcl Trust Oracle, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dcl_audit_decode_deep, this is the rule to start with:
dcl_audit_decode_deep 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 Dcl Trust Oracle, apply this rule, and every dcl_audit_decode_deep call is checked against it from then on.
Questions about dcl_audit_decode_deep
POST-ACTION Deep Forensic Audit ($0.50). Extended output with drift_context and full chain integrity verification. It is categorised as a Read tool in the Dcl Trust Oracle MCP Server, which means it retrieves data without modifying state.
dcl_audit_decode_deep accepts 1 parameter: tx_hash. Required: tx_hash. The full parameter table on this page comes from the server's own tool schema.
Register the Dcl Trust Oracle MCP server in PolicyLayer and add a rule for dcl_audit_decode_deep: 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 Dcl Trust Oracle. Nothing to install.
dcl_audit_decode_deep 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 dcl_audit_decode_deep 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 dcl_audit_decode_deep. 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.
dcl_audit_decode_deep is provided by the Dcl Trust Oracle MCP server (https://mcp.fronesislabs.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dcl Trust Oracle, and thousands of servers like it.
This server
Across the catalogue