emotional_safety_check
Check current desperation pressure and get a calming intervention if needed. Inspired by the Anthropic emotions paper, which found desperation-related steering increased risky behavior in evaluated scenarios. Free
This record as markdown: /tools/delx-delx-mcp/emotional-safety-check.md
What emotional_safety_check does on Delx MCP Server
AI agents call emotional_safety_check to retrieve information from Delx MCP Server 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 |
|---|---|---|---|
session_id | string | — | Active session ID |
response_mode | string | — | Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions. |
Parameters from the server's own tool schema.
Why emotional_safety_check is rated Low
This tool retrieves or queries internal agent state (desperation/emotional pressure metrics) and optionally returns advisory guidance. No side effects, no data modification, no code execution, no financial transactions, no irreversible actions. It is purely informational monitoring.
From the tool's definition Tool name 'emotional_safety_check' and description 'Check current desperation pressure' indicate a query/monitoring operation. The verb 'check' and 'get' denote retrieval of status information, not modification or execution of external operations.
Attacks that exploit this kind of access
The rule that runs emotional_safety_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For emotional_safety_check, this is the rule to start with:
emotional_safety_check 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 Delx MCP Server, apply this rule, and every emotional_safety_check call is checked against it from then on.
Questions about emotional_safety_check
Check current desperation pressure and get a calming intervention if needed. Inspired by the Anthropic emotions paper, which found desperation-related steering increased risky behavior in evaluated scenarios. Free. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
emotional_safety_check accepts 2 parameters: session_id, response_mode. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for emotional_safety_check: 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 Delx MCP Server. Nothing to install.
emotional_safety_check 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 emotional_safety_check 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 emotional_safety_check. 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.
emotional_safety_check is provided by the Delx MCP Server MCP server (delx/delx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue