surface_relevant_context
AI agents call surface_relevant_context 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.
Despite the empty description lowering confidence slightly, the verb 'surface' combined with the noun 'context' and the broader server design (indexed PDF library with citations, local-first architecture) strongly indicates a read operation that retrieves relevant information from indexed or stored context. This aligns with the Read category for data retrieval with no side effects.
From the tool's definition Tool name 'surface_relevant_context' indicates retrieval or querying of context information. The empty description and pattern of sibling tools (add_* and aggregate_* functions) suggest this tool retrieves or surfaces stored context without modifying data.
Attacks that exploit this kind of access
surface_relevant_context. 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 surface_relevant_context: 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.
surface_relevant_context 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 surface_relevant_context 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 surface_relevant_context. 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.
surface_relevant_context 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 →