Search across ALL logged sessions using semantic similarity.
AI agents call search_all_sessions to retrieve information from Opencode Personal Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries session data using semantic search. It has no side effects, does not create, modify, or delete data, and does not execute external operations or commit financial transactions. It is a pure read operation that matches the 'Read' category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'.
From the tool's definition Tool performs 'Search across ALL logged sessions using semantic similarity' - a query operation with no modification or destructive capability.
Documented attack patterns abuse exactly the kind of access search_all_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Opencode Personal Knowledge, and nothing reaches the server without passing your rules. This is the rule we recommend for search_all_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"search_all_sessions": {}
}
}search_all_sessions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search across ALL logged sessions using semantic similarity. It is categorised as a Read tool in the Opencode Personal Knowledge MCP Server, which means it retrieves data without modifying state.
Register the Opencode Personal Knowledge MCP server in PolicyLayer and add a rule for search_all_sessions: 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 Personal Knowledge. Nothing to install.
search_all_sessions 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_all_sessions 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_all_sessions. 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_all_sessions is provided by the Opencode Personal Knowledge MCP server (nocturnlabs/opencode-personal-knowledge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Opencode Personal Knowledge, 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.
15 Opencode Personal Knowledge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.