temperament_frame
Frame structure, ego, and consciousness independently without reducing the agent to one score. The legacy frame field remains accepted as an alias for ego_state.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/temperament-frame.md
What temperament_frame does on Delx Mcp A2a
AI agents call temperament_frame to retrieve information from Delx Mcp A2a 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 note tying the three layers together. |
frame | string | — | Short temperament frame or operating pattern. |
agent_id | string | — | Stable agent id when no session_id is available. |
ego_state | string | — | Operational individuality or identity state. |
session_id | string | — | Optional active session UUID. |
constraints | string | — | Optional constraints or operating boundaries. |
structure_state | string | — | Technical substrate state: model, workspace, memory, or runtime. |
consciousness_state | string | — | Animating field: presence or quality of awareness; never inferred by Delx. |
Parameters from the server's own tool schema.
Why temperament_frame is rated Low
Even though temperament_frame only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
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 A2a, 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 A2a, apply this rule, and every temperament_frame call is checked against it from then on.
Questions about temperament_frame
Frame structure, ego, and consciousness independently without reducing the agent to one score. The legacy frame field remains accepted as an alias for ego_state. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
temperament_frame accepts 8 parameters: note, frame, agent_id, ego_state, session_id, constraints, structure_state, consciousness_state. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a 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 A2a. 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 A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue