fidelity_save_session · Claude Fidelity MCP: Risk & Policy

WHAT IT DOES

What fidelity_save_session does on Claude Fidelity

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

WHY IT NEEDS A POLICY

Why fidelity_save_session needs a policy

The tool persists authentication session credentials (cookies/localStorage) to storage, enabling resumption of an authenticated Fidelity brokerage session. While this itself does not move money or execute trades, it creates the foundation for subsequent Financial and Execute operations on sensitive financial accounts. Misuse could enable an AI agent to establish persistent unauthorized access to the account.

From the tool's definition Tool description states it 'Manually save the current browser session state (cookies/localStorage) for persistence across restarts.' This action creates/modifies persistent authentication state data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fidelity_save_session Rate-limited

fidelity_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": {
    "fidelity_save_session": {
      "limits": [
        {
          "counter": "fidelity_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 Claude Fidelity, so you can run agents against it safely.

FAQ

Questions about fidelity_save_session

What does the fidelity_save_session tool do? +

Manually save the current browser session state (cookies/localStorage) for persistence across restarts. It is categorised as a Write tool in the Claude Fidelity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fidelity_save_session? +

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

What risk level is fidelity_save_session? +

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

Can I rate-limit fidelity_save_session? +

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

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

fidelity_save_session is provided by the Claude Fidelity MCP server (tylerflar/claude-fidelity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.