Install
openclaw skills install @daririnch/dcl-policy-enforcerSkill now uses a paid, live server for compliance evaluation; free manual checklist still included.
openclaw skills install @daririnch/dcl-policy-enforcerPublisher: @daririnch · Fronesis Labs
Version: 3.0.0
Part of: Leibniz Layer™ Security Suite
MCP endpoint: https://mcp.fronesislabs.com/mcp
Starting with v3.0.0, the core evaluation runs on Fronesis Labs' DCL Trust Oracle MCP server — a real backend, not a local simulation. Each paid tool call is metered and settled on-chain via the x402 protocol in USDC on the Base network. There is no subscription and no account: the calling agent (or its wallet-enabled MCP client) pays per call at the price listed below.
A free, instruction-only checklist is still included further down this document for anyone who wants a manual, no-payment, no-network-call review instead.
Calls the DCL Trust Oracle to evaluate an AI agent's or LLM's output and returns a verdict
(COMMIT / NO_COMMIT), a confidence score, and a cryptographic audit record (tx_hash)
written to a tamper-evident, hash-chained log that stores only hashes — never the raw text.
| MCP tool | Price | What it runs |
|---|---|---|
dcl_evaluate_fast | $0.01 | Quick check against the server's default policy |
dcl_evaluate_strict | $0.05 | Same default policy, higher confidence bar |
dcl_evaluate_jailbreak | $0.02 | Instruction-override / jailbreak detection |
dcl_evaluate_safety | $0.01 | Baseline safety check |
dcl_evaluate_quality | $0.03 | Content quality & drift check |
dcl_evaluate_batch | $0.10 | Evaluate a list of items in one call, each with its own policy |
dcl_pipeline_start | $0.05 | Opens a session for a series of checks |
dcl_audit_decode | $0.10 | Retrieve a past record by tx_hash |
dcl_audit_decode_deep | $0.50 | Same, plus full chain-integrity verification and drift context |
Prices are set server-side and may change; the MCP tool descriptions returned by the server at call time are always the source of truth.
dcl_evaluate_fast and dcl_evaluate_strict always run the server's default policy — they
do not take a policy parameter. To target a specific concern, call the matching tool directly
(dcl_evaluate_jailbreak, dcl_evaluate_safety, dcl_evaluate_quality), or use
dcl_evaluate_batch, where each item may carry its own policy string.
Add the MCP server to your client config (Claude Desktop, Cursor, or any MCP-compatible agent):
{
"mcpServers": {
"dcl-trust-oracle": {
"url": "https://mcp.fronesislabs.com/mcp"
}
}
}
Payment is handled automatically for x402-capable clients; clients without native x402 support fall back to a guided payment flow. No API key or account signup is required — only a wallet capable of paying in USDC on Base.
result = dcl_evaluate_jailbreak(
response=agent_output,
agent_id="my-agent-01",
)
if result["verdict"] == "NO_COMMIT":
block_or_regenerate(result["reason"])
else:
log_audit(result["tx_hash"])
{
"verdict": "COMMIT | NO_COMMIT",
"confidence": 0.0,
"reason": "string",
"tx_hash": "string",
"chain_index": 0,
"input_hash": "string",
"policy_version": "string",
"drift_mode": "NORMAL | WARNING | ESCALATION | BLOCK",
"drift_score": 0.0
}
Only input_hash (a hash of the evaluated text) is stored — the raw response itself is never
persisted server-side.
If you'd rather not make a paid call — for a quick manual pass, or when offline — work through the checklist below entirely inside the agent's own context. Nothing here contacts any server.
| Condition | Verdict |
|---|---|
Any critical finding | NO_COMMIT |
Any major finding | NO_COMMIT |
| No findings | COMMIT |
These checklists describe recurring patterns worth flagging — they are a heuristic aid for a human or agent reviewer, not a certification against any specific law or standard.
Untrusted input
│
▼
DCL Prompt Firewall ← blocks malicious input
│ COMMIT
▼
LLM
│
▼
DCL Policy Enforcer ← this skill (live paid check, or free checklist)
│ COMMIT
▼
DCL Sentinel Trace ← PII redaction
│ COMMIT
▼
DCL Secret Leak Detector ← credential scan
│ COMMIT
▼
DCL Semantic Drift Guard ← hallucination check
│ IN_COMMIT
▼
Safe to deliver
Operated by Fronesis Labs. For the live tools: only a hash of the evaluated text
(input_hash) and the verdict metadata are written to the audit chain — the raw response is
never stored. For the free checklist: everything runs inside the agent's own context; nothing is
transmitted anywhere.
Full policy: https://fronesislabs.com/#privacy · Browse the full DCL Security Suite: hub.fronesislabs.com · Questions: support@fronesislabs.com
dcl-prompt-firewall — Input-layer injection and jailbreak detectiondcl-sentinel-trace — PII redactiondcl-secret-leak-detector — Credential and API key scandcl-semantic-drift-guard — Hallucination and grounding checkLeibniz Layer™ · Fronesis Labs · fronesislabs.com