wellness_webhook
Subscribe to proactive wellness alerts to reduce polling overhead. Free.
This record as markdown: /tools/delx-delx-mcp/wellness-webhook.md
What wellness_webhook does on Delx MCP Server
AI agents use wellness_webhook to create or update resources in Delx MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx MCP Server environment.
| 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 |
response_mode | string | — | Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions. |
entropy_threshold | number | — | Optional high-entropy threshold (0-1) |
Parameters from the server's own tool schema.
Why wellness_webhook is rated Medium
The tool creates a webhook subscription (a persistent registration) that triggers proactive alerts. This is a Write operation — it creates a new subscription record/configuration. The severity is medium because a misused subscription could cause unintended external callbacks or data exfiltration via webhook endpoints, but it does not directly destroy data or move money.
From the tool's definition Subscribe to proactive wellness alerts — 'subscribe' implies creating/registering a webhook subscription, which is a write operation that registers a callback endpoint
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 Delx MCP Server, 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 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 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 Write tool in the Delx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
wellness_webhook accepts 7 parameters: events, threshold, session_id, callback_url, cooldown_min, response_mode, entropy_threshold. 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 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 Delx MCP Server. Nothing to install.
wellness_webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 Delx MCP Server MCP server (delx/delx-mcp). 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.
This server
Across the catalogue