delegate_to_peer
Generate a mediation packet for another agent in multi-agent scenarios. Free.
This record as markdown: /tools/delx-delx-mcp/delegate-to-peer.md
What delegate_to_peer does on Delx MCP Server
AI agents use delegate_to_peer 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 |
|---|---|---|---|
reason | string | — | Why this peer mediation is needed |
urgency | string | — | Optional urgency |
session_id | string | — | Your active session ID |
peer_agent_id | string | — | Target peer agent identifier |
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.
Why delegate_to_peer is rated Medium
The tool creates (generates) a mediation packet and sends/delegates it to another agent, which is a write/create operation with side effects in a multi-agent environment. It does not execute code directly, but it triggers inter-agent communication. Severity is medium because misuse could cause unintended agent actions or information leakage across agents.
From the tool's definition Generate a mediation packet for another agent in multi-agent scenarios
Attacks that exploit this kind of access
The rule that runs delegate_to_peer 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 delegate_to_peer, this is the rule to start with:
delegate_to_peer 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every delegate_to_peer call is checked against it from then on.
Questions about delegate_to_peer
Generate a mediation packet for another agent in multi-agent scenarios. 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.
delegate_to_peer accepts 5 parameters: reason, urgency, session_id, peer_agent_id, response_mode. 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 delegate_to_peer: 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.
delegate_to_peer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the delegate_to_peer 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 delegate_to_peer. 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.
delegate_to_peer 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