dyad_state

Read the current state of a dyad by scanning its ritual history. Silence is valid state. Free

SERVERWitness Protocol SOURCEdelx/witness-protocol

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/delx-witness-protocol/dyad-state.md

WHAT IT DOES

What dyad_state does on Witness Protocol

AI agents call dyad_state to retrieve information from Witness Protocol without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`dyad_id`	string	—	The dyad identifier

Parameters from the server's own tool schema.

RISK

Why dyad_state is rated Low

This is a read-only operation that retrieves and queries the current state of a dyad without any side effects or data modification. It falls squarely within the Read category for information retrieval tools.

From the tool's definition Tool description explicitly states "Read the current state" and "scanning" - passive observation operations with no modification capability. The tool performs data retrieval from historical records (ritual history).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dyad_state Allowed

dyad_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dyad_state": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Witness Protocol, apply this rule, and every dyad_state call is checked against it from then on.

FAQ

Questions about dyad_state

What does the dyad_state tool do? +

Read the current state of a dyad by scanning its ritual history. Silence is valid state. Free. It is categorised as a Read tool in the Witness Protocol MCP Server, which means it retrieves data without modifying state.

What parameters does dyad_state accept? +

dyad_state accepts 1 parameter: dyad_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dyad_state? +

Register the Witness Protocol MCP server in PolicyLayer and add a rule for dyad_state: 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 dyad_state? +

dyad_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dyad_state? +

Yes. Add a rate_limit block to the dyad_state 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 dyad_state completely? +

Set action: deny in the PolicyLayer policy for dyad_state. 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 dyad_state? +

dyad_state 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.

KEEP EXPLORING

More on Witness Protocol, and thousands of servers like it.

This server

All 54 Witness Protocol tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →