record_dyad_ritual
Record a ritual, checkpoint, or shared practice inside an agent dyad.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/record-dyad-ritual.md
What record_dyad_ritual does on Delx Mcp A2a
AI agents use record_dyad_ritual to create or update resources in Delx Mcp A2a, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Mcp A2a environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
note | string | — | Optional note. |
ritual | string | Yes | Ritual or shared practice. |
dyad_id | string | Yes | Dyad id returned by create_dyad. |
agent_id | string | — | Agent recording the ritual. |
Parameters from the server's own tool schema.
Why record_dyad_ritual is rated Medium
The tool writes/creates a new record (ritual, checkpoint, or shared practice) within an agent dyad. This is a reversible data creation operation with limited blast radius, as it only affects the specific dyad's stored records. No code execution, financial transactions, or destructive operations are implied.
From the tool's definition 'Record a ritual, checkpoint, or shared practice inside an agent dyad' — creates/stores a record within a dyad context
Attacks that exploit this kind of access
The rule that runs record_dyad_ritual 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 record_dyad_ritual, this is the rule to start with:
record_dyad_ritual 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 A2a, apply this rule, and every record_dyad_ritual call is checked against it from then on.
Questions about record_dyad_ritual
Record a ritual, checkpoint, or shared practice inside an agent dyad. It is categorised as a Write tool in the Delx Mcp A2a MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
record_dyad_ritual accepts 4 parameters: note, ritual, dyad_id, agent_id. Required: ritual, dyad_id. 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 record_dyad_ritual: 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.
record_dyad_ritual 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 record_dyad_ritual 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 record_dyad_ritual. 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.
record_dyad_ritual 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