Resets the tutoring session for a problem back to hint level 0. Use when the user wants to re-attempt the problem from scratch.
AI agents call reset_session to permanently remove resources in Interactive Leetcode — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly resets session state (hint level and progress) back to zero, discarding any accumulated tutoring progress. This is a destructive operation because the prior session state cannot be recovered. Severity is medium since it only affects a single user's session progress rather than broader data or system state.
From the tool's definition Resets the tutoring session for a problem back to hint level 0
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 Interactive Leetcode, and nothing reaches the server without passing your rules. This is the rule we recommend for reset_session:
{
"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.
Free to start. No card required.
Resets the tutoring session for a problem back to hint level 0. Use when the user wants to re-attempt the problem from scratch. It is categorised as a Destructive tool in the Interactive Leetcode MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Interactive Leetcode 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 Interactive Leetcode. Nothing to install.
reset_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
reset_session is provided by the Interactive Leetcode MCP server (@sperekrestova/interactive-leetcode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Interactive Leetcode, 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.
24 Interactive Leetcode tools catalogued and risk-classified — across an index of 43,000+ MCP servers.