batch_wellness_check
Check wellness scores for multiple sessions in one call. Useful for multi-agent orchestration. Free.
This record as markdown: /tools/delx-witness-protocol/batch-wellness-check.md
What batch_wellness_check does on Witness Protocol
AI agents call batch_wellness_check to retrieve information from Witness Protocol 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 | — | 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 retrieves or queries wellness score data across multiple sessions without modifying, deleting, or executing external operations. The description explicitly frames it as a checking/reporting function useful for orchestration monitoring. No irreversible actions, financial implications, or code execution are indicated. The 'free' designation further suggests informational use only.
From the tool's definition Tool name 'batch_wellness_check' and description 'Check wellness scores for multiple sessions in one call' indicate a read-only query operation that retrieves wellness data with no stated 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 Witness Protocol, 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 Witness Protocol, apply this rule, and every batch_wellness_check call is checked against it from then on.
Questions about batch_wellness_check
Check wellness scores for multiple sessions in one call. Useful for multi-agent orchestration. Free. It is categorised as a Read tool in the Witness Protocol MCP Server, which means it retrieves data without modifying state.
batch_wellness_check accepts 2 parameters: session_ids, include_entropy. The full parameter table on this page comes from the server's own tool schema.
Register the Witness Protocol 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 Witness Protocol. 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 Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Witness Protocol, and thousands of servers like it.
This server
Across the catalogue