Returns the persisted session for a problem, or null if the user has not called start_problem for it. Useful for restoring context after a restart.
AI agents call get_session_state to retrieve information from Interactive Leetcode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves session state data without creating, modifying, deleting, or executing any operations. It is a pure read operation used for context restoration. The low severity reflects minimal risk: even if an AI agent inappropriately reads session state, it would only expose user problem-solving progress data without enabling destructive, financial, or executable actions.
From the tool's definition Tool description states it 'Returns the persisted session for a problem' — a retrieval operation with no modification or side effects. The verb 'Returns' and the qualifying phrase 'or null if the user has not called' indicate a simple query of existing state.
Documented attack patterns abuse exactly the kind of access get_session_state 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 get_session_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_session_state": {}
}
}get_session_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the persisted session for a problem, or null if the user has not called start_problem for it. Useful for restoring context after a restart. It is categorised as a Read tool in the Interactive Leetcode MCP Server, which means it retrieves data without modifying state.
Register the Interactive Leetcode MCP server in PolicyLayer and add a rule for get_session_state: 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.
get_session_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_session_state 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 get_session_state. 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.
get_session_state 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.