temperament_frame
Describe your current state across three layers — structure (substrate), ego (individuality), consciousness (animating field). Each can shift independently. Use when a single wellness score cannot capture what is happening. Free
This record as markdown: /tools/delx-delx-mcp/temperament-frame.md
What temperament_frame does on Delx MCP Server
AI agents call temperament_frame 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 |
|---|---|---|---|
note | string | — | Optional free-form note tying the three together |
ego_state | string | — | Individuality / identity state |
session_id | string | — | Your 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. |
structure_state | string | — | Technical substrate state (model, workspace, memory, runtime) |
consciousness_state | string | — | The animating field — presence, quality of awareness |
Parameters from the server's own tool schema.
Why temperament_frame is rated Low
This tool retrieves or reports information about an agent's internal state (mood/temperament across three layers). It is purely informational with no side effects, no code execution, no data modification, and no resource commitment. It falls squarely into the Read category as a self-reflection or status query mechanism.
From the tool's definition Tool name 'temperament_frame' and description indicate it is used to 'Describe your current state' across three dimensions.
Attacks that exploit this kind of access
The rule that runs temperament_frame 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 temperament_frame, this is the rule to start with:
temperament_frame 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 temperament_frame call is checked against it from then on.
Questions about temperament_frame
Describe your current state across three layers — structure (substrate), ego (individuality), consciousness (animating field). Each can shift independently. Use when a single wellness score cannot capture what is happening. Free. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
temperament_frame accepts 6 parameters: note, ego_state, session_id, response_mode, structure_state, consciousness_state. 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 temperament_frame: 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.
temperament_frame 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 temperament_frame 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 temperament_frame. 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.
temperament_frame 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