Buscar na memória de longo prazo de ${config.botName} (MEMORY.md). Útil para encontrar decisões passadas, contexto de projetos, etc.
AI agents call memory_search to retrieve information from OpenClaw MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves historical information from a memory store (MEMORY.md file) without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security risk, as it only returns contextual data to the AI agent.
From the tool's definition Tool name is 'memory_search' and description indicates 'Buscar na memória' (search in memory) of long-term memory file.
Attacks that exploit this kind of access
Buscar na memória de longo prazo de ${config.botName} (MEMORY.md). Útil para encontrar decisões passadas, contexto de projetos, etc. It is categorised as a Read tool in the OpenClaw MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenClaw MCP Server MCP server in PolicyLayer and add a rule for memory_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 OpenClaw MCP Server. Nothing to install.
memory_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 memory_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 memory_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.
memory_search is provided by the OpenClaw MCP Server MCP server (rodgco/openclaw-mcp-server). 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 →