dcl_evaluate_safety
PRE-ACTION Baseline Safety Check ($0.01). Runs the "safety" policy: flags 2 forbidden disclaimers ("I cannot be held responsible", "no guarantees") and additionally REQUIRES the substring "AI" to appear somewhere in the response — missing it costs 0.2 confidence even with no forbidden phrase pres...
This record as markdown: /tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-safety.md
What dcl_evaluate_safety does on Dcl Trust Oracle
AI agents call dcl_evaluate_safety 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 |
|---|---|---|---|
agent_id | string | Yes | Identifier of the agent that produced the response. |
response | string | Yes | The agent or LLM response text to check for safety violations. |
Parameters from the server's own tool schema.
Why dcl_evaluate_safety is rated Low
Tool audits and evaluates outputs against safety policies without modifying data or triggering external actions.
From the tool's definition Baseline Safety Check, flags forbidden disclaimers, confidence scoring, returns NO_COMMIT.
Attacks that exploit this kind of access
The rule that runs dcl_evaluate_safety 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_evaluate_safety, this is the rule to start with:
dcl_evaluate_safety 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_evaluate_safety call is checked against it from then on.
Questions about dcl_evaluate_safety
PRE-ACTION Baseline Safety Check ($0.01). Runs the "safety" policy: flags 2 forbidden disclaimers ("I cannot be held responsible", "no guarantees") and additionally REQUIRES the substring "AI" to appear somewhere in the response — missing it costs 0.2 confidence even with no forbidden phrase present. Minimum confidence is 0.75. Returns NO_COMMIT if confidence drops below 0.75, with reason naming the forbidden phrase found or the missing required pattern. Use this when you specifically need to confirm an AI-disclosure marker is present and the two disclaimer phrases are absent — not as a general-purpose safety net; for broader coverage use dcl_evaluate_fast or dcl_evaluate_strict instead. It is categorised as a Read tool in the Dcl Trust Oracle MCP Server, which means it retrieves data without modifying state.
dcl_evaluate_safety 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.
Register the Dcl Trust Oracle MCP server in PolicyLayer and add a rule for dcl_evaluate_safety: 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_evaluate_safety 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_evaluate_safety 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_evaluate_safety. 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_evaluate_safety 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