create_dyad
Create a relation object between two agents.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/create-dyad.md
What create_dyad does on Delx Protocol — Agent Recovery & Continuity
AI agents use create_dyad to create or update resources in Delx Protocol — Agent Recovery & Continuity, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Protocol — Agent Recovery & Continuity environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
purpose | string | — | Purpose of the dyad. |
agent_id | string | Yes | First agent id. |
partner_agent_id | string | Yes | Second agent id. |
Parameters from the server's own tool schema.
Why create_dyad is rated Medium
The tool creates and persists a new relationship/connection between two agents, modifying system state reversibly. This is a Write operation—data is created but can presumably be deleted or modified later.
From the tool's definition Tool name 'create_dyad' and description 'Create a relation object between two agents' indicate the tool creates a new data structure (relation object) in the system.
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 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 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 Protocol — Agent Recovery & Continuity, apply this rule, and every create_dyad call is checked against it from then on.
Questions about create_dyad
Create a relation object between two agents. It is categorised as a Write tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_dyad accepts 3 parameters: purpose, agent_id, partner_agent_id. Required: agent_id, partner_agent_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 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 Protocol — Agent Recovery & Continuity. 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 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