revoke_range_from_user
Revoke range access from a user.
This record as markdown: /tools/tjnull-ludus-fastmcp/revoke-range-from-user.md
What revoke_range_from_user does on Ludus FastMCP
AI agents call revoke_range_from_user 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 revoke_range_from_user is rated Critical
Revoking access is a destructive, hard-to-reverse operation. While it doesn't delete data outright, it removes a user's permissions/access to their range, which could disrupt active security research or testing. In IAM contexts, revocation is typically treated as destructive because restoring access requires explicit re-granting.
From the tool's definition 'Revoke range access from a user' — removing access is an irreversible administrative action that cuts off a user's ability to interact with their cyber range environment
Attacks that exploit this kind of access
The rule that runs revoke_range_from_user 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 revoke_range_from_user, this is the rule to start with:
revoke_range_from_user 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 revoke_range_from_user call is checked against it from then on.
Questions about revoke_range_from_user
Revoke range access from a user. 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 revoke_range_from_user: 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.
revoke_range_from_user 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 revoke_range_from_user 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 revoke_range_from_user. 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.
revoke_range_from_user 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