save_session_log · Network Device Assistant MCP

WHAT IT DOES

What save_session_log does on Network Device Assistant

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

WHY IT NEEDS A POLICY

Why save_session_log needs a policy

This tool writes data (command history log) to a new file. It is reversible (the file can be deleted), has no destructive impact, does not execute commands, and does not move money. The blast radius of misuse is minimal—an attacker could fill disk space or expose session history, but this is a low-severity Write operation.

From the tool's definition Tool description states 'Save the full command history of a session to a timestamped Markdown' — creates a new file with session data. The verb 'save' and creation of a timestamped output file indicate data creation/writing.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_session_log Rate-limited

save_session_log 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": {
    "save_session_log": {
      "limits": [
        {
          "counter": "save_session_log_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 Network Device Assistant, so you can run agents against it safely.

FAQ

Questions about save_session_log

What does the save_session_log tool do? +

Save the full command history of a session to a timestamped Markdown. It is categorised as a Write tool in the Network Device Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_session_log? +

Register the Network Device Assistant MCP server in PolicyLayer and add a rule for save_session_log: 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 Network Device Assistant. Nothing to install.

What risk level is save_session_log? +

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

Can I rate-limit save_session_log? +

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

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

save_session_log is provided by the Network Device Assistant MCP server (mgarabito/network-device-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.