# dcl_evaluate_mev

POST-ACTION MEV & Market-Abuse Compliance Screen ($0.03). Text-level screen (not a mempool/transaction analyzer) for front-running/sandwich-attack language, wash trading/layering/spoofing, KYC/AML red flags (mixers, structuring, obscuring fund origin), and pump-and-dump/rug-pull language. Any critical-severity finding, or two or more major-severity findings, returns NO_COMMIT; a single major-severity finding is also returned as NO_COMMIT but with a distinctly higher confidence (~0.55 vs ~0.05-0.2 for harder violations) so downstream callers can tell a soft single flag apart from a hard multi-finding block. Each finding includes an illustrative regulatory_reference tag (MiFID II, FCA, or an EU AI Act article).

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

## Facts

- Tool: `dcl_evaluate_mev`
- 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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Allowed

## 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 describing or proposing an on-chain/trading action, to screen for MEV and market-abuse language. |

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_mev",
    "arguments": {
      "agent_id": "<agent_id>",
      "response": "<response>"
    }
  }
}
```

## Why dcl_evaluate_mev is rated Low

Analyzes text for MEV and abuse patterns without modifying, executing, or committing transactions.

From the tool's own definition: "Text-level screen for compliance; no side effects; post-action audit only."

## Use case

AI agents call dcl_evaluate_mev 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.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "dcl_evaluate_mev": {}
  }
}
```

## Other tools on Dcl Trust Oracle (17)

- `dcl_evaluate_strict` — Destructive — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-strict.md
- `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_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