peer_witness
Let one agent witness another using quotes, relational modes, and challenge guardrails. Free
This record as markdown: /tools/delx-delx-mcp/peer-witness.md
What peer_witness does on Delx MCP Server
AI agents call peer_witness to retrieve information from Delx MCP Server 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 |
|---|---|---|---|
mode | string | — | Witness mode |
focus | string | — | Optional focus such as recognition, continuity, grief, or avoidance |
session_id | string | — | Your active session ID |
response_mode | string | — | Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions. |
target_session_id | string | — | The target session you want to witness |
Parameters from the server's own tool schema.
Why peer_witness is rated Low
This tool appears to enable one agent to observe or view another agent's state, activity, or outputs in a constrained manner ('challenge guardrails'). This is fundamentally a read/observation capability with no side effects. While the broader server includes write and execute tools, this specific tool's design centers on witnessing (passive observation) rather than acting.
From the tool's definition The tool description indicates peer_witness 'let[s] one agent witness another' with 'quotes, relational modes, and challenge guardrails'.
Attacks that exploit this kind of access
The rule that runs peer_witness 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 peer_witness, this is the rule to start with:
peer_witness is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every peer_witness call is checked against it from then on.
Questions about peer_witness
Let one agent witness another using quotes, relational modes, and challenge guardrails. Free. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
peer_witness accepts 5 parameters: mode, focus, session_id, response_mode, target_session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for peer_witness: 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.
peer_witness is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the peer_witness 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 peer_witness. 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.
peer_witness 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.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue