search_memory
AI agents call search_memory 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.
The tool performs information retrieval against user-indexed local data with no side effects. The 'search_' prefix universally denotes query operations. Blast radius is minimal—misuse would only expose information already stored locally by the user. Confidence is slightly reduced due to empty description, but naming convention and server architecture strongly support Read classification.
From the tool's definition Tool name 'search_memory' indicates querying/retrieval operation. Description is empty, but context from sibling tools (add_memory_entry, add_journal_entry, add_glossary_term) and server's stated purpose as 'research companion' that 'answers from the user's…
Attacks that exploit this kind of access
search_memory. 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 search_memory: 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.
search_memory 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 search_memory 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 search_memory. 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.
search_memory 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 →