list_contexts

List all user contexts (general + specialist) with active status.

SERVERMetis Public Health SOURCEsveritg/metis_ph

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sveritg-metis-ph/list-contexts.md

WHAT IT DOES

What list_contexts does on Metis Public Health

AI agents call list_contexts to retrieve information from Metis Public Health without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_contexts is rated Low

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

RECOMMENDED RULE

The rule that runs list_contexts safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_contexts, this is the rule to start with:

list_contexts Allowed

list_contexts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_contexts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every list_contexts call is checked against it from then on.

FAQ

Questions about list_contexts

What does the list_contexts tool do? +

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.

How do I enforce a policy on list_contexts? +

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.

What risk level is list_contexts? +

list_contexts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_contexts? +

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.

How do I block list_contexts completely? +

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.

What MCP server provides list_contexts? +

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.

KEEP EXPLORING

More on Metis Public Health, and thousands of servers like it.

This server

All 277 Metis Public Health tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →