import_session · COAIA Sequential Thinking MCP

WHAT IT DOES

What import_session does on COAIA Sequential Thinking

AI agents use import_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.

WHY IT NEEDS A POLICY

Why import_session needs a policy

The import operation creates or populates session data from an external source, which is a modification operation. While the blast radius is limited by the fact that sessions are typically isolated user contexts and the operation is reversible, a malicious import could inject unwanted thinking states or corrupt session logic.

From the tool's definition Tool description states 'Import a thinking session from a file' — this creates or modifies data by loading external content into the system. The action is reversible (a session can be cleared or overwritten), making it Write rather than Destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_session Rate-limited

import_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_session": {
      "limits": [
        {
          "counter": "import_session_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches COAIA Sequential Thinking, so you can run agents against it safely.

FAQ

Questions about import_session

What does the import_session tool do? +

Import a thinking session from 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.

How do I enforce a policy on import_session? +

Register the COAIA Sequential Thinking MCP server in PolicyLayer and add a rule for import_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.

What risk level is import_session? +

import_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_session? +

Yes. Add a rate_limit block to the import_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.

How do I block import_session completely? +

Set action: deny in the PolicyLayer policy for import_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.

What MCP server provides import_session? +

import_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.