scout_save_session · Scout MCP: Risk & Policy

WHAT IT DOES

What scout_save_session does on Scout

AI agents use scout_save_session to create or update resources in Scout — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scout environment.

WHY IT NEEDS A POLICY

Why scout_save_session needs a policy

This tool writes sensitive session data (cookies, localStorage) to disk. While not destructive (data can be deleted/overwritten) and not immediately financial, it creates persistent records of authentication credentials and user state that could be misused if accessed by an attacker or malicious agent. The high severity reflects that saved sessions enable session hijacking and unauthorized access to user accounts.

From the tool's definition Tool name 'scout_save_session' and description 'Save the current browser session (cookies, localStorage) to a named file' indicate creation/persistence of session state data to storage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scout_save_session Rate-limited

scout_save_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": {
    "scout_save_session": {
      "limits": [
        {
          "counter": "scout_save_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 Scout, so you can run agents against it safely.

FAQ

Questions about scout_save_session

What does the scout_save_session tool do? +

Save the current browser session (cookies, localStorage) to a named file. It is categorised as a Write tool in the Scout MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on scout_save_session? +

Register the Scout MCP server in PolicyLayer and add a rule for scout_save_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 Scout. Nothing to install.

What risk level is scout_save_session? +

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

Can I rate-limit scout_save_session? +

Yes. Add a rate_limit block to the scout_save_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 scout_save_session completely? +

Set action: deny in the PolicyLayer policy for scout_save_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 scout_save_session? +

scout_save_session is provided by the Scout MCP server (lautrek/scout). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.