reset_sage_session

THE RISK

Critical Risk

Why reset_sage_session needs a policy

Resetting the session state irreversibly destroys all persistent variables, computations, and context accumulated across prior tool calls. The server description emphasizes 'persistent state across tool calls' as a key feature, so resetting it is a non-recoverable destructive action. Severity is medium since it only affects the in-memory session state, not permanent stored data.

From the tool's definition Reset the SageMath session state for the current MCP session

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

POLICY

How to control reset_sage_session

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

policy.json

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

reset_sage_session 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 SageMath MCP Server — 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

Related tools and policies

More SageMath MCP Server tools

Execute cancel_sage_session Cancel any running Sage computation and restart the worker Execute evaluate_sage_streaming Execute SageMath code and stream intermediate print() output Execute boolean_algebra_operation Boolean algebra: operations on boolean polynomials Execute calculate_expression Evaluate a SageMath expression and return numeric/string forms Execute coding_theory_operation Coding theory: construct error-correcting codes Execute combinatorics_operation Combinatorics: binomial, permutations, combinations, partitions, and more Execute differentiate_expression Differentiate an expression with respect to a variable Execute distribution_operation Probability distribution operations: PDF, CDF, quantile, mean, variance, sampling

All 32 SageMath MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in SageMath MCP Server → 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.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about reset_sage_session

What does the reset_sage_session tool do? +

Reset the SageMath session state for the current MCP session. It is categorised as a Destructive tool in the SageMath MCP Server 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_sage_session? +

Register the SageMath MCP Server MCP server in PolicyLayer and add a rule for reset_sage_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 SageMath MCP Server. Nothing to install.

What risk level is reset_sage_session? +

reset_sage_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_sage_session? +

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

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

reset_sage_session is provided by the SageMath MCP Server MCP server (xbp-europe/sagemath-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SageMath MCP Server tool call.

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

CHECK YOUR STACK →