clear_range_access

Clear all range access permissions.

SERVERLudus FastMCP SOURCEtjnull/ludus-fastmcp

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/tjnull-ludus-fastmcp/clear-range-access.md

WHAT IT DOES

What clear_range_access does on Ludus FastMCP

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.

RISK

Why clear_range_access is rated Critical

This tool destroys access permissions in a way that cannot be trivially undone without administrative intervention. While it does not delete data or infrastructure directly, clearing all access permissions is an irreversible action that disables functionality for potentially all users in the system.

From the tool's definition clear_range_access — 'Clear all range access permissions' irreversibly removes access controls, preventing legitimate users from reaching resources they depend on.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_range_access 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 clear_range_access, this is the rule to start with:

clear_range_access Hidden

clear_range_access 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_range_access"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about clear_range_access

What does the clear_range_access tool do? +

Clear all range access permissions. 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.

How do I enforce a policy on clear_range_access? +

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.

What risk level is clear_range_access? +

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.

Can I rate-limit clear_range_access? +

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.

How do I block clear_range_access completely? +

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.

What MCP server provides clear_range_access? +

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.

KEEP EXPLORING

More on Ludus Fast, and thousands of servers like it.

This server

All 231 Ludus Fast tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →