Export the current thinking session to a file.
AI agents use export_session to create or update resources in COAIA Sequential Thinking — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your COAIA Sequential Thinking environment.
This tool creates a new file containing session data. While this is a write operation, the severity is low because it only exports existing data that the user has already created in the current session—it does not modify critical data, delete anything, or affect systems beyond the user's local file system.
From the tool's definition Tool exports data to a file, which is a write operation that creates or modifies file system state. The description explicitly states 'Export the current thinking session to a file.'
Attacks that exploit this kind of access
Export the current thinking session to a file. It is categorised as a Write tool in the COAIA Sequential Thinking MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the COAIA Sequential Thinking MCP server in PolicyLayer and add a rule for 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 COAIA Sequential Thinking. Nothing to install.
export_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 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 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.
export_session is provided by the COAIA Sequential Thinking MCP server (miadisabelle/mcp-coaia-sequential-thinking). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →