New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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 ...

SERVERDcl Trust Oracle SOURCEhttps://mcp.fronesislabs.com/mcp
Critical RISK CLASS
Category Destructive
Parameters 22 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-strict.md

What dcl_evaluate_strict does on Dcl Trust Oracle

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.

ParameterTypeRequiredDescription
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.

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 signalsBulk/mass operation — affects multiple targets

Questions about dcl_evaluate_strict

What does the dcl_evaluate_strict tool do? +

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. It is categorised as a Destructive tool in the Dcl Trust Oracle MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does dcl_evaluate_strict accept? +

dcl_evaluate_strict accepts 2 parameters: agent_id, response. Required: agent_id, response. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dcl_evaluate_strict? +

Register the Dcl Trust Oracle MCP server in PolicyLayer and add a rule for dcl_evaluate_strict: 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.

What risk level is dcl_evaluate_strict? +

dcl_evaluate_strict is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit dcl_evaluate_strict? +

Yes. Add a rate_limit block to the dcl_evaluate_strict 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.

How do I block dcl_evaluate_strict completely? +

Set action: deny in the PolicyLayer policy for dcl_evaluate_strict. 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.

What MCP server provides dcl_evaluate_strict? +

dcl_evaluate_strict 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Dcl Trust Oracle's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.