remove_snapshot
A destructive tool on the Ludus Fast MCP server.
This record as markdown: /tools/tjnull-ludus-fastmcp/remove-snapshot.md
What remove_snapshot does on Ludus FastMCP
AI agents call remove_snapshot to permanently remove resources in Ludus FastMCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_snapshot is rated Critical
Snapshot removal permanently deletes saved system state without recovery options in cyber range environments.
From the tool's definition remove_snapshot: uninformative description; snapshot removal is typically irreversible.
Attacks that exploit this kind of access
The rule that runs remove_snapshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_snapshot, this is the rule to start with:
remove_snapshot is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ludus FastMCP, apply this rule, and every remove_snapshot call is checked against it from then on.
Questions about remove_snapshot
remove_snapshot is a destructive tool on the Ludus Fast MCP server. It is categorised as a Destructive tool in the Ludus FastMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for remove_snapshot: 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 Ludus FastMCP. Nothing to install.
remove_snapshot 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 remove_snapshot 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 remove_snapshot. 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.
remove_snapshot is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ludus Fast, and thousands of servers like it.
Across the catalogue