Start logging a new session for later search. IMPORTANT: After starting, you MUST call log_message for EACH user message and your response to capture the conversation. Call this when the user wants to record an important conversation.
AI agents use start_logging_session 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 a new logging session record in the local knowledge store. It is a reversible write operation (sessions can be deleted) with no code execution, financial impact, or destructive behavior. The blast radius is low since it only initializes a local session entry.
From the tool's definition Start logging a new session for later search... Call this when the user wants to record an important conversation.
Documented attack patterns abuse exactly the kind of access start_logging_session 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 start_logging_session:
{
"version": "1",
"default": "deny",
"tools": {
"start_logging_session": {
"limits": [
{
"counter": "start_logging_session_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}start_logging_session 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.
Start logging a new session for later search. IMPORTANT: After starting, you MUST call log_message for EACH user message and your response to capture the conversation. Call this when the user wants to record an important conversation. 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 start_logging_session: 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.
start_logging_session 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 start_logging_session 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 start_logging_session. 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.
start_logging_session 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.