AI agents call opencode_export_session 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.
Exporting a session as JSON is a read/retrieval operation - it reads session data and serializes it to JSON format without modifying or deleting anything. Severity is low as it only reads session data, though there could be some sensitivity if session data contains code or credentials.
From the tool's definition Export an OpenCode session as JSON
Documented attack patterns abuse exactly the kind of access opencode_export_session gives an agent:
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 opencode_export_session:
{
"version": "1",
"default": "deny",
"tools": {
"opencode_export_session": {}
}
}opencode_export_session 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.
Export an OpenCode session as JSON. It is categorised as a Read tool in the OpenCode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenCode MCP Server MCP server in PolicyLayer and add a rule for opencode_export_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 MCP Server. Nothing to install.
opencode_export_session 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 opencode_export_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 opencode_export_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.
opencode_export_session is provided by the OpenCode MCP Server MCP server (nosolosoft/opencode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.
6 OpenCode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.