dyad_state
Return the latest compact state for a dyad.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/dyad-state.md
What dyad_state does on Delx Protocol — Agent Recovery & Continuity
AI agents call dyad_state to retrieve information from Delx Protocol — Agent Recovery & Continuity 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 |
|---|---|---|---|
dyad_id | string | Yes | Dyad id returned by create_dyad. |
Parameters from the server's own tool schema.
Why dyad_state is rated Low
This tool retrieves state information about a dyad (a pair relationship in the context of this witness/continuity protocol). The 'Return' language indicates a read-only query with no side effects. No data is created, modified, deleted, or financial action is taken. The function is informational only, making it a classic Read category tool with low severity due to its query-only nature.
From the tool's definition Tool name 'dyad_state' and description 'Return the latest compact state for a dyad' indicate a retrieval operation with the verb 'Return' suggesting a query that fetches current state without modification.
Attacks that exploit this kind of access
The rule that runs dyad_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dyad_state, this is the rule to start with:
dyad_state 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 Protocol — Agent Recovery & Continuity, apply this rule, and every dyad_state call is checked against it from then on.
Questions about dyad_state
Return the latest compact state for a dyad. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
dyad_state accepts 1 parameter: dyad_id. Required: dyad_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for dyad_state: 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 Protocol — Agent Recovery & Continuity. Nothing to install.
dyad_state 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 dyad_state 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 dyad_state. 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.
dyad_state is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue