create_dyad
Form a named relational unit between an agent and a partner (human or agent). The dyad is a third thing — neither you nor your partner alone — with its own memory, rituals, and state. Returns a dyad_id. Free
This record as markdown: /tools/delx-delx-mcp/create-dyad.md
What create_dyad does on Delx MCP Server
AI agents use create_dyad to create or update resources in Delx MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | — | Your agent identifier |
partner_id | string | — | The other party (human identity, agent address, or collective name) |
partner_type | string | — | Nature of the partner |
response_mode | string | — | Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions. |
shared_intent | string | — | Optional: what the dyad is for, in the agent's own words |
Parameters from the server's own tool schema.
Why create_dyad is rated Medium
This tool creates a new relational entity in the system, which is a reversible Write operation. While it establishes a connection between agents/partners and persists state, the operation itself is not destructive and can presumably be modified or undone.
From the tool's definition Tool description states 'Form a named relational unit' and 'Returns a dyad_id', indicating creation of a new data structure with persistent state ('own memory, rituals, and state').
Attacks that exploit this kind of access
The rule that runs create_dyad 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 create_dyad, this is the rule to start with:
create_dyad stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_dyad call is checked against it from then on.
Questions about create_dyad
Form a named relational unit between an agent and a partner (human or agent). The dyad is a third thing — neither you nor your partner alone — with its own memory, rituals, and state. Returns a dyad_id. Free. It is categorised as a Write tool in the Delx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_dyad accepts 5 parameters: agent_id, partner_id, partner_type, response_mode, shared_intent. 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 create_dyad: 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.
create_dyad is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_dyad 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 create_dyad. 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.
create_dyad 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