Critical Risk →

reset_session

Reset a session

How to control reset_session ↓

AI agents call reset_session to permanently remove resources in NotebookLM MCP Structured — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Resetting a session implies destroying the current session state irreversibly. Session data, authentication tokens, and any in-progress work would be lost and cannot be recovered. This is a destructive action with no indication of reversibility. Confidence is moderate because the description is minimal and does not clarify exactly what data is lost.

From the tool's definition reset_session - 'Reset a session'

Documented attack patterns abuse exactly the kind of access reset_session gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and NotebookLM MCP Structured, and nothing reaches the server without passing your rules. This is the rule we recommend for reset_session:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset_session"
  ]
}

reset_session disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register NotebookLM MCP Structured — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the reset_session tool do? +

Reset a session. It is categorised as a Destructive tool in the NotebookLM MCP Structured MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reset_session? +

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

What risk level is reset_session? +

reset_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reset_session? +

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

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

reset_session is provided by the NotebookLM MCP Structured MCP server (paolodalprato/notebooklm-mcp-structured). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NotebookLM MCP Structured tool call.

Deterministic rules across all 15 NotebookLM MCP Structured tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

15 NotebookLM MCP Structured tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.