List the ${LANG_CODES.length} supported languages (ISO-639-1 code + English name + native label). Default:
AI agents call list_languages 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 tool performs a simple data retrieval operation without modifying, executing code, deleting, or committing financial transactions. It returns informational reference data about available language options. The pay-per-call pricing model of the server is a business concern but does not change the technical classification of this specific tool's operation.
From the tool's definition Tool name 'list_languages' and description indicate it retrieves/queries a list of supported languages with metadata (ISO-639-1 codes, English names, native labels).
Attacks that exploit this kind of access
List the ${LANG_CODES.length} supported languages (ISO-639-1 code + English name + native label). Default:. 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_languages: 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_languages 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_languages 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_languages. 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_languages 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 →