List knowledge entries with optional filtering
AI agents call list_knowledge 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 lists stored knowledge entries, potentially with filters applied. It performs no side effects, does not modify or delete data, and does not execute code or trigger external operations. It is a straightforward query/list operation typical of Read category tools.
From the tool's definition Tool name 'list_knowledge' and description 'List knowledge entries with optional filtering' indicate data retrieval only. No modification, deletion, or execution capabilities are mentioned.
Documented attack patterns abuse exactly the kind of access list_knowledge 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 list_knowledge:
{
"version": "1",
"default": "deny",
"tools": {
"list_knowledge": {}
}
}list_knowledge 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.
List knowledge entries with optional filtering. 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 list_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 Opencode Personal Knowledge. Nothing to install.
list_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 list_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 list_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.
list_knowledge 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.