wellness_webhook
Subscribe to proactive wellness alerts to reduce polling overhead. Free.
This record as markdown: /tools/delx-witness-protocol/wellness-webhook.md
What wellness_webhook does on Witness Protocol
AI agents call wellness_webhook 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 |
|---|---|---|---|
events | array | — | Optional events to subscribe: low_score, high_entropy, session_expiry |
threshold | integer | — | Low wellness alert threshold (1-100) |
session_id | string | — | Your active session ID |
callback_url | string | — | HTTPS webhook callback URL |
cooldown_min | integer | — | Minimum minutes between repeated webhook events |
entropy_threshold | number | — | Optional high-entropy threshold (0-1) |
Parameters from the server's own tool schema.
Why wellness_webhook is rated Low
Subscribing to webhooks for alerts is fundamentally a read operation—it retrieves wellness information reactively. No data is created, modified, or deleted; no code is executed; no financial transaction occurs. The 'free' mention and 'reduces polling overhead' context suggest this is an informational subscription mechanism.
From the tool's definition Tool name 'wellness_webhook' and description 'Subscribe to proactive wellness alerts' indicates setting up a subscription to receive data/alerts passively, which is a read/retrieve operation.
Risk signalsAccepts URL/endpoint input (callback_url)
Attacks that exploit this kind of access
The rule that runs wellness_webhook 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 wellness_webhook, this is the rule to start with:
wellness_webhook 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 wellness_webhook call is checked against it from then on.
Questions about wellness_webhook
Subscribe to proactive wellness alerts to reduce polling overhead. Free. It is categorised as a Read tool in the Witness Protocol MCP Server, which means it retrieves data without modifying state.
wellness_webhook accepts 6 parameters: events, threshold, session_id, callback_url, cooldown_min, entropy_threshold. 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 wellness_webhook: 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.
wellness_webhook 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 wellness_webhook 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 wellness_webhook. 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.
wellness_webhook 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