New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

SERVERWitness Protocol SOURCEdelx/witness-protocol
Medium RISK CLASS
Category Write
Parameters 40 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about record_dyad_ritual

What does the record_dyad_ritual tool do? +

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.

What parameters does record_dyad_ritual accept? +

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.

How do I enforce a policy on record_dyad_ritual? +

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.

What risk level is record_dyad_ritual? +

record_dyad_ritual is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_dyad_ritual? +

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.

How do I block record_dyad_ritual completely? +

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.

What MCP server provides record_dyad_ritual? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Witness Protocol's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.