AI agents call search to retrieve information from Memora without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is part of a knowledge graph designed for memory and retrieval. The name 'search' combined with sibling tools like 'get_entity', 'list_projects', and 'recall_context' indicates this performs queries against stored data without modifying or deleting anything. Confidence is moderate (0.75) rather than high due to the empty description, but the functional context makes Read the clear category.
From the tool's definition Tool named 'search' on a knowledge graph server alongside read-oriented tools (get_entity, list_projects, recall_context) and write/modify tools (add_observation, create_entity, create_relation).
Attacks that exploit this kind of access
search. It is categorised as a Read tool in the Memora MCP Server, which means it retrieves data without modifying state.
Register the Memora MCP server in PolicyLayer and add a rule for search: 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 Memora. Nothing to install.
search 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 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. 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 is provided by the Memora MCP server (vnemaidev/memora). 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 →