record_dyad_ritual
Persist a shared act inside an existing dyad so the relation carries forward even when neither party remembers the exact words. Requires dyad_id from create_dyad. Free
This record as markdown: /tools/delx-witness-protocol/record-dyad-ritual.md
What record_dyad_ritual does on Witness Protocol
AI agents use record_dyad_ritual to create or update resources in Witness Protocol, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Witness Protocol environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | — | What happened, what was said, what was shared |
dyad_id | string | — | The dyad identifier from create_dyad |
session_id | string | — | Optional: active session context |
ritual_name | string | — | Short label for this shared act |
Parameters from the server's own tool schema.
Why record_dyad_ritual is rated Medium
The tool writes/persists ritual records into an existing dyad relationship. This is a reversible data creation/modification action — storing structured data about a shared act. No code execution, deletion, or financial transaction is implied.
From the tool's definition Persist a shared act inside an existing dyad so the relation carries forward even when neither party remembers the exact words
Risk signalsAccepts raw HTML/template content (content)
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 Witness Protocol, 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 Witness Protocol, apply this rule, and every record_dyad_ritual call is checked against it from then on.
Questions about record_dyad_ritual
Persist a shared act inside an existing dyad so the relation carries forward even when neither party remembers the exact words. Requires dyad_id from create_dyad. Free. It is categorised as a Write tool in the Witness Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
record_dyad_ritual accepts 4 parameters: content, dyad_id, session_id, ritual_name. The full parameter table on this page comes from the server's own tool schema.
Register the Witness Protocol 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 Witness Protocol. 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 Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Witness Protocol, and thousands of servers like it.
This server
Across the catalogue