Store a new knowledge entry in your personal knowledge base. Use this to save important information, notes, or learnings for later retrieval.
AI agents use store_knowledge to create or update resources in Opencode Personal Knowledge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Opencode Personal Knowledge environment.
This tool creates or modifies data (a knowledge entry) in the user's personal knowledge base. It is reversible since the sibling tools include 'delete_knowledge', which can undo storage operations.
From the tool's definition Tool description states 'Store a new knowledge entry in your personal knowledge base. Use this to save important information, notes, or learnings for later retrieval.' The verb 'Store' combined with 'save' indicates persistent data creation/modification…
Documented attack patterns abuse exactly the kind of access store_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 store_knowledge:
{
"version": "1",
"default": "deny",
"tools": {
"store_knowledge": {
"limits": [
{
"counter": "store_knowledge_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}store_knowledge stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Store a new knowledge entry in your personal knowledge base. Use this to save important information, notes, or learnings for later retrieval. It is categorised as a Write tool in the Opencode Personal Knowledge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Opencode Personal Knowledge MCP server in PolicyLayer and add a rule for store_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.
store_knowledge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the store_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 store_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.
store_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.