session_progress_clear

Clear session progress entries. With no

SERVERJshookmcp SOURCE@jshookmcp/jshook

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-vmoranv-jshookmcp/session-progress-clear.md

WHAT IT DOES

What session_progress_clear does on Jshookmcp

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

RISK

Why session_progress_clear is rated Critical

Permanently removes session progress data; cannot be recovered once deleted.

From the tool's definition clear session progress entries, irreversible deletion without undo

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session_progress_clear safely

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

session_progress_clear Hidden

session_progress_clear 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": [
    "session_progress_clear"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about session_progress_clear

What does the session_progress_clear tool do? +

Clear session progress entries. With no. It is categorised as a Destructive tool in the Jshookmcp 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 session_progress_clear? +

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

What risk level is session_progress_clear? +

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

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

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

session_progress_clear is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → Critical-risk tools on this server →

Across the catalogue

clear-session on CodeAnalysis MCP Server →clear_project_index on ACE-MCP →clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

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