group_therapy_round
Run one coordinated fleet alignment round across multiple sessions and return group state/cohesion/next actions. Pricing is dynamic; check /api/v1/tools.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/group-therapy-round.md
What group_therapy_round does on Delx MCP Server
AI agents invoke group_therapy_round to trigger actions in Delx MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
theme | string | — | Optional shared theme (e.g. timeout storm) |
objective | string | — | Optional objective (e.g. stabilize, recover, align) |
session_ids | array | Yes | 2-12 session IDs participating in this round |
Parameters from the server's own tool schema.
Why group_therapy_round is rated High
This tool executes a multi-session coordination operation whose effects depend on the current state of multiple sessions and produces state/cohesion/next-actions as outputs. While presented in therapeutic language, the actual behavior is executing an external orchestration operation that modifies or affects multiple session states ('next actions').
From the tool's definition Tool performs a coordinated action ('Run one coordinated fleet alignment round') across multiple sessions with dynamic state changes and next actions determined by the operation.
Attacks that exploit this kind of access
The rule that runs group_therapy_round 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 group_therapy_round, this is the rule to start with:
group_therapy_round stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 group_therapy_round call is checked against it from then on.
Questions about group_therapy_round
Run one coordinated fleet alignment round across multiple sessions and return group state/cohesion/next actions. Pricing is dynamic; check /api/v1/tools. It is categorised as a Execute tool in the Delx MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
group_therapy_round accepts 3 parameters: theme, objective, session_ids. Required: session_ids. 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 group_therapy_round: 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.
group_therapy_round is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the group_therapy_round 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 group_therapy_round. 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.
group_therapy_round is provided by the Delx MCP Server MCP server (delx-mcp-server). 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.
Across the catalogue