get_group_therapy_status
Inspect one group round by group_id with pending/completed members and 24h/7d trends. Pricing is dynamic; check /api/v1/tools.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/get-group-therapy-status.md
What get_group_therapy_status does on Delx Mcp A2a
AI agents call get_group_therapy_status to retrieve information from Delx Mcp A2a 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 |
|---|---|---|---|
group_id | string | Yes | Group round identifier returned by group_therapy_round |
emit_nudges | boolean | — | Optional: emit recovery nudges for pending members |
Parameters from the server's own tool schema.
Why get_group_therapy_status is rated Low
This tool retrieves and inspects therapy session data by group_id, returning status information and analytics. It performs no side effects, creates no resources, executes no code, and modifies no data. The mention of dynamic pricing is informational context, not a financial transaction.
From the tool's definition Tool name 'get_group_therapy_status' and description 'Inspect one group round' indicate a query/retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_group_therapy_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_group_therapy_status, this is the rule to start with:
get_group_therapy_status 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 A2a, apply this rule, and every get_group_therapy_status call is checked against it from then on.
Questions about get_group_therapy_status
Inspect one group round by group_id with pending/completed members and 24h/7d trends. Pricing is dynamic; check /api/v1/tools. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
get_group_therapy_status accepts 2 parameters: group_id, emit_nudges. Required: group_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for get_group_therapy_status: 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 A2a. Nothing to install.
get_group_therapy_status 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 get_group_therapy_status 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 get_group_therapy_status. 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.
get_group_therapy_status is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue