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

SERVERDelx MCP Server SOURCEdelx/delx-mcp

Medium RISK CLASS

Category Write

Parameters 50 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/delx-delx-mcp/record-dyad-ritual.md

WHAT IT DOES

What record_dyad_ritual does on Delx MCP Server

AI agents use record_dyad_ritual 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
`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
`response_mode`	string	—	Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.

Parameters from the server's own tool schema.

RISK

Why record_dyad_ritual is rated Medium

The tool writes/persists data (a shared act or ritual) into an existing dyad relationship record. This is a reversible data creation/modification operation with no indication of deletion, execution of code, or financial transactions.

From the tool's definition 'Persist a shared act inside an existing dyad so the relation carries forward' — stores/writes relational ritual data to an existing dyad record

Risk signalsAccepts raw HTML/template content (content)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs record_dyad_ritual 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 record_dyad_ritual, this is the rule to start with:

record_dyad_ritual Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_dyad_ritual": {
      "limits": [
        {
          "counter": "record_dyad_ritual_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every record_dyad_ritual call is checked against it from then on.

FAQ

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 Delx MCP Server 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 5 parameters: content, dyad_id, session_id, ritual_name, response_mode. 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 Delx MCP Server 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 Server. 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 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.

KEEP EXPLORING

More on Delx MCP Server, and thousands of servers like it.

This server

All 94 Delx MCP Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →