Low Risk

search_memory

Searches the semantic memory for specific information without refining a prompt.

How to control search_memory ↓

What search_memory does on OpenCode MCP Server

AI agents call search_memory to retrieve information from OpenCode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_memory needs a policy

This tool queries stored semantic memory to retrieve information. It performs no side effects, does not modify or delete data, and does not execute external operations. It is a straightforward read operation analogous to a search or get function.

From the tool's definition Tool description states it 'Searches the semantic memory for specific information' — a pure retrieval operation with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access search_memory gives an agent:

How to control search_memory

PolicyLayer is an MCP gateway — it sits between your AI agents and OpenCode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_memory:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_memory": {}
  }
}

search_memory is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OpenCode MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_memory

What does the search_memory tool do? +

Searches the semantic memory for specific information without refining a prompt. It is categorised as a Read tool in the OpenCode MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_memory? +

Register the OpenCode MCP Server 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 OpenCode MCP Server. Nothing to install.

What risk level is search_memory? +

search_memory is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_memory? +

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.

How do I block search_memory completely? +

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.

What MCP server provides search_memory? +

search_memory is provided by the OpenCode MCP Server MCP server (marlondivino/open-code-as-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenCode MCP Server tool call.

Start from OpenCode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

5 OpenCode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.