Daily average wellness trend for an institution.
AI agents call get_institution_trend_daily to retrieve information from Wellness Pulse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to fetch aggregated wellness trend data. It retrieves and returns information without modifying any underlying data, executing external commands, or triggering side effects. The sibling tools (all prefixed with 'get_') and the server's stated purpose of 'transforming wellbeing data into real-time insights' further confirm this is a data retrieval mechanism.
From the tool's definition Tool name is 'get_institution_trend_daily' and description states it retrieves 'Daily average wellness trend for an institution' — a data retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Daily average wellness trend for an institution. It is categorised as a Read tool in the Wellness Pulse MCP Server, which means it retrieves data without modifying state.
Register the Wellness Pulse MCP server in PolicyLayer and add a rule for get_institution_trend_daily: 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 Wellness Pulse. Nothing to install.
get_institution_trend_daily 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_institution_trend_daily 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_institution_trend_daily. 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_institution_trend_daily is provided by the Wellness Pulse MCP server (prmail/wellness-pulse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →