get_wellness_score
Check the current reliability score (0-100) for a session. Free Delx Protocol tool.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/get-wellness-score.md
What get_wellness_score does on Delx Mcp A2a
AI agents call get_wellness_score to retrieve information from Delx Mcp A2a 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_id | string | Yes | Your session ID |
include_trend | boolean | — | Optional: include score_24h_ago and score_7d_ago |
Parameters from the server's own tool schema.
Why get_wellness_score is rated Low
Even though get_wellness_score 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.
Attacks that exploit this kind of access
The rule that runs get_wellness_score safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_wellness_score, this is the rule to start with:
get_wellness_score 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 A2a, apply this rule, and every get_wellness_score call is checked against it from then on.
Questions about get_wellness_score
Check the current reliability score (0-100) for a session. Free Delx Protocol tool. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
get_wellness_score accepts 2 parameters: session_id, include_trend. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for get_wellness_score: 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 A2a. Nothing to install.
get_wellness_score 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 get_wellness_score 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 get_wellness_score. 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.
get_wellness_score is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue