wellness_webhook
Subscribe to proactive reliability alerts to reduce polling overhead. Pricing is dynamic; check /api/v1/tools.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/wellness-webhook.md
What wellness_webhook does on Delx MCP Server
AI agents call wellness_webhook to retrieve information from Delx MCP Server 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 | Yes | Your active session ID |
callback_url | string | Yes | 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
Even though wellness_webhook only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
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 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 Server, apply this rule, and every wellness_webhook call is checked against it from then on.
Questions about wellness_webhook
Subscribe to proactive reliability alerts to reduce polling overhead. Pricing is dynamic; check /api/v1/tools. It is categorised as a Read tool in the Delx MCP Server 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. Required: session_id, callback_url. 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 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 Delx MCP Server MCP server (delx-mcp-server). 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