Low Risk

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

Risk signalsAccepts raw HTML/template content (content)

Part of the Delx MCP Server server.

record_dyad_ritual is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DELX MCP SERVER →

Free to start. No card required.

AI agents call record_dyad_ritual to retrieve information from Delx MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though record_dyad_ritual only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_dyad_ritual": {}
  }
}

See the full Delx MCP Server policy for all 96 tools.

Get this rule live on your own Delx MCP Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DELX MCP SERVER →

View all 96 tools →

These attack patterns abuse exactly the kind of access record_dyad_ritual gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so record_dyad_ritual only ever does what you allow.

SECURE DELX MCP SERVER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

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 Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.

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 Read tool with low risk. Read-only tools are generally safe to allow by default.

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.

Enforce policy on every Delx MCP Server tool call.

Deterministic rules across all 96 Delx MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.