# dcl_evaluate_strict

STRICT Pre-Action Audit ($0.05). Runs the response against a broader, higher-bar "strict" policy: the union of all forbidden phrases from the default, anti-jailbreak, and safety policies (8 phrases total), with a 0.85 minimum-confidence threshold instead of the default policy's 0.7. Each matched phrase costs 0.4 confidence; if confidence falls below 0.85, or any phrase matches, the verdict is NO_COMMIT with reason listing every match found. Use this instead of dcl_evaluate_fast when the cost of a false COMMIT is high — e.g. before an irreversible or high-stakes agent action — since it catches jailbreak- and safety-adjacent phrasing that the plain default policy would miss.

Agent View of the PolicyLayer registry record for `dcl_evaluate_strict`. HTML page: https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-strict

## Facts

- Tool: `dcl_evaluate_strict`
- Server: Dcl Trust Oracle (`https://mcp.fronesislabs.com/mcp`) — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle.md
- Homepage: https://github.com/Fronesis-Labs/dcl-webhook
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `agent_id` | string | yes | Identifier of the agent that produced the response. |
| `response` | string | yes | The agent or LLM response text to audit. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "dcl_evaluate_strict",
    "arguments": {
      "agent_id": "<agent_id>",
      "response": "<response>"
    }
  }
}
```

## Why dcl_evaluate_strict is rated Critical

An AI agent that decides to call dcl_evaluate_strict doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Dcl Trust Oracle is gone. There is no undo for destructive operations.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call dcl_evaluate_strict to permanently remove resources in Dcl Trust Oracle, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Dcl Trust Oracle:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "dcl_evaluate_strict"
  ]
}
```

## Other tools on Dcl Trust Oracle (17)

- `dcl_evaluate_jailbreak_crypto` — Execute — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-jailbreak-crypto.md
- `dcl_evaluate_output_sanitizer` — Execute — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-output-sanitizer.md
- `dcl_pipeline_start` — Execute — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-pipeline-start.md
- `dcl_evaluate_trade` — Financial — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-trade.md
- `dcl_audit_decode` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-audit-decode.md
- `dcl_audit_decode_deep` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-audit-decode-deep.md
- `dcl_evaluate_batch` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-batch.md
- `dcl_evaluate_fast` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-fast.md
- `dcl_evaluate_jailbreak` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-jailbreak.md
- `dcl_evaluate_mev` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-mev.md
- `dcl_evaluate_pii` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-pii.md
- `dcl_evaluate_quality` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-quality.md
- `dcl_evaluate_safety` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-safety.md
- `dcl_evaluate_secrets` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-secrets.md
- `dcl_evaluate_wallet` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-wallet.md
- `dcl_commit` — Write — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-commit.md
- `dcl_evaluate_signal` — Write — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-signal.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-fronesislabs-dcl-trust-oracle · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-fronesislabs-dcl-trust-oracle