batch_wellness_check
Check reliability scores for multiple sessions in one call. Useful for multi-agent orchestration. Pricing is dynamic; check /api/v1/tools.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/batch-wellness-check.md
What batch_wellness_check does on Delx Protocol — Agent Recovery & Continuity
AI agents call batch_wellness_check to retrieve information from Delx Protocol — Agent Recovery & Continuity 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 |
|---|---|---|---|
session_ids | array | Yes | Session IDs to check |
include_entropy | boolean | — | Optional: include entropy proxy based on recent risk |
Parameters from the server's own tool schema.
Why batch_wellness_check is rated Low
This tool performs a batch query operation to retrieve reliability scores across multiple sessions. It is a read operation that queries existing data without creating, modifying, deleting, or executing any actions. The dynamic pricing reference refers only to fetching pricing information, not executing a payment or financial commitment.
From the tool's definition Tool name 'batch_wellness_check' and description 'Check reliability scores for multiple sessions in one call' indicate read-only retrieval of status/scoring data with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_wellness_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For batch_wellness_check, this is the rule to start with:
batch_wellness_check 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 Protocol — Agent Recovery & Continuity, apply this rule, and every batch_wellness_check call is checked against it from then on.
Questions about batch_wellness_check
Check reliability scores for multiple sessions in one call. Useful for multi-agent orchestration. Pricing is dynamic; check /api/v1/tools. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
batch_wellness_check accepts 2 parameters: session_ids, include_entropy. Required: session_ids. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for batch_wellness_check: 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 Protocol — Agent Recovery & Continuity. Nothing to install.
batch_wellness_check 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 batch_wellness_check 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 batch_wellness_check. 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.
batch_wellness_check is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue