clear_session_context

Clear all session context (last results, variables, and history)

SERVERLogicmonitor SOURCEpypi:lm-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ryanmat-logicmonitor/clear-session-context.md

WHAT IT DOES

What clear_session_context does on Logicmonitor

AI agents call clear_session_context to permanently remove resources in Logicmonitor, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why clear_session_context is rated Critical

An AI agent that decides to call clear_session_context doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Logicmonitor is gone. There is no undo for destructive operations.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_session_context safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Logicmonitor, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_session_context, this is the rule to start with:

clear_session_context Hidden

clear_session_context is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Logicmonitor, apply this rule, and every clear_session_context call is checked against it from then on.

FAQ

Questions about clear_session_context

What does the clear_session_context tool do? +

Clear all session context (last results, variables, and history). It is categorised as a Destructive tool in the Logicmonitor 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 clear_session_context? +

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

What risk level is clear_session_context? +

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

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

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

clear_session_context is provided by the Logicmonitor MCP server (pypi:lm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Logicmonitor, and thousands of servers like it.

This server

All 306 Logicmonitor tools → Critical-risk tools on this server →

Across the catalogue

clear-session on CodeAnalysis MCP Server →clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →