List all user contexts (general + specialist) with active status.
AI agents call list_contexts to retrieve information from Metis Public Health without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about user contexts. It performs a read-only operation that retrieves data from the system's context store. The 'list' operation is inherently non-destructive and produces no side effects beyond data retrieval. No data is created, modified, deleted, or executed, making this clearly a Read operation with low severity.
From the tool's definition Tool name 'list_contexts' and description 'List all user contexts (general + specialist) with active status' indicates retrieval and enumeration of existing data without modification, deletion, or execution.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all user contexts (general + specialist) with active status. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for list_contexts: 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 Metis Public Health. Nothing to install.
list_contexts 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_contexts 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_contexts. 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_contexts is provided by the Metis Public Health MCP server (sveritg/metis_ph). 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 →