List the ${AUDIENCE_IDS.length} supported audiences (human, agent).
AI agents call list_audiences to retrieve information from Wellness Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward query operation that retrieves and enumerates supported audiences without modifying data, executing code, or incurring costs. The read-only nature and informational purpose place it clearly in the Read category with low severity.
From the tool's definition Tool name 'list_audiences' and description 'List the supported audiences' indicate a retrieval operation with no side effects. Returns static metadata about supported audience types (human, agent).
Attacks that exploit this kind of access
List the ${AUDIENCE_IDS.length} supported audiences (human, agent). It is categorised as a Read tool in the Wellness Manager MCP Server, which means it retrieves data without modifying state.
Register the Wellness Manager MCP server in PolicyLayer and add a rule for list_audiences: 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 Manager. Nothing to install.
list_audiences 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 list_audiences 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 list_audiences. 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.
list_audiences is provided by the Wellness Manager MCP server (wellnessagent/wellness-master). 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 →