Clear all range access permissions. Args: user_id: Optional user ID (admin only) Returns: Clear result
AI agents call clear_range_access 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.
Clearing all range access permissions is an irreversible bulk operation that removes all access controls for a cyber range environment. This cannot be easily undone and could lock out all users or expose systems, making it a destructive action with high blast radius.
From the tool's definition Clear all range access permissions
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Documented attack patterns abuse exactly the kind of access clear_range_access gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ludus FastMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_range_access:
{
"version": "1",
"default": "deny",
"hide": [
"clear_range_access"
]
} clear_range_access disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear all range access permissions. Args: user_id: Optional user ID (admin only) Returns: Clear result. 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 clear_range_access: 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.
clear_range_access 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 clear_range_access 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 clear_range_access. 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.
clear_range_access 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.
Deterministic rules across all 201 Ludus FastMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
201 Ludus FastMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.