Critical Risk →

reset_session

Reset the current audit session.

How to control reset_session ↓

What reset_session does on Blind-Auditor-MCP

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

Critical Risk

Why reset_session needs a policy

Resetting a session destroys in-progress work (submitted drafts, audit results, context isolation state) and cannot be undone. This is an irreversible operation on the current session state, placing it in the Destructive category. Severity is medium because the blast radius is limited to the current audit session rather than persistent stored data, but misuse by an AI agent could silently wipe audit progress.

From the tool's definition 'Reset the current audit session' — resetting a session irreversibly discards current state, progress, and context of the audit session.

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

How to control reset_session

PolicyLayer is an MCP gateway — it sits between your AI agents and Blind-Auditor-MCP, 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 Blind-Auditor-MCP — 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.

Related tools and policies

Go deeper

Questions about reset_session

What does the reset_session tool do? +

Reset the current audit session. It is categorised as a Destructive tool in the Blind-Auditor-MCP 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 Blind-Auditor- 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 Blind-Auditor-MCP. 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 Blind-Auditor- MCP server (sim-xia/blind-auditor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Blind-Auditor-MCP tool call.

Start from Blind-Auditor-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

4 Blind-Auditor-MCP tools catalogued and risk-classified — across an index of 43,000+ 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.