Semantic search across an Anima
AI agents call search_knowledge to retrieve information from Elephantasm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs semantic searching across stored knowledge/memories, which is a read-only retrieval operation. There is no indication of data creation, modification, deletion, code execution, or financial operations. The blast radius of misuse is minimal—an agent could retrieve information it shouldn't access, but cannot alter or destroy data, execute code, or cause financial harm.
From the tool's definition Tool name is 'search_knowledge' and description indicates 'Semantic search across an Anima' (memory database). The function retrieves or queries data without modification or side effects.
Attacks that exploit this kind of access
Semantic search across an Anima. It is categorised as a Read tool in the Elephantasm MCP Server, which means it retrieves data without modifying state.
Register the Elephantasm MCP server in PolicyLayer and add a rule for search_knowledge: 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 Elephantasm. Nothing to install.
search_knowledge 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_knowledge 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_knowledge. 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_knowledge is provided by the Elephantasm MCP server (kaminocorp/elephantasm-mcp). 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 →