lattice_reset

THE RISK

Critical Risk

This tool irreversibly clears all handles and bindings accumulated during an analysis session. While the underlying document is preserved, any intermediate analysis state, bindings, and handles cannot be recovered after reset. This qualifies as Destructive due to the irreversible loss of session state, though severity is medium since the source document itself is retained.

From the tool's definition 'Clear all handles and bindings' — removes existing state/bindings irreversibly; 'start fresh analysis' implies prior work is lost

Risk signalsBulk/mass operation — affects multiple targets

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

HOW TO CONTROL LATTICE_RESET

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "lattice_reset"
  ]
}

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

Create a free account and register Lattice — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Lattice tools

Destructive lattice_memo_delete Delete a memo that is no longer needed to free memory. Use this when context becomes stal Execute nucleus_execute Execute Nucleus commands directly on a document without LLM orchestration. Execute analyze_document Analyze a document using the Recursive Language Model (RLM). Execute lattice_llm_batch_respond Resolve a pending (llm_batch …) suspension with all N responses at once. (llm_batch COLL Execute lattice_llm_respond Resolve a pending (llm_query …) suspension with a single string response. When lattice_qu Execute lattice_query Execute a Nucleus query on the loaded document. Write lattice_close Close the current session and free memory. Read lattice_bindings Show current handle bindings. Returns all active handles with their stubs: $grep_error:

All 15 Lattice tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Lattice → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the lattice_reset tool do? +

Clear all handles and bindings but keep the document loaded. Use this to start fresh analysis. It is categorised as a Destructive tool in the Lattice 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 lattice_reset? +

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

What risk level is lattice_reset? +

lattice_reset 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 lattice_reset? +

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

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

lattice_reset is provided by the Lattice MCP server (yogthos/matryoshka). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Lattice tool call.

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

GOVERN LATTICE →

Free to start. No card required.

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

// WHAT LATTICE_RESET ON LATTICE DOES

// THE RISK

// HOW TO CONTROL LATTICE_RESET

// EXPLORE