List all deployed ranges for a user, showing current status and basic information.
AI agents call list_user_ranges to retrieve information from LudusMCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about deployed ranges for a user. It performs a read-only query operation that returns status and basic information without creating, modifying, deleting, or executing any changes to the training environment. The blast radius of misuse is minimal—an attacker could only gain visibility into what ranges exist and their status, not manipulate or destroy infrastructure.
From the tool's definition Tool name 'list_user_ranges' and description 'List all deployed ranges for a user, showing current status and basic information' indicate a query/retrieval operation with no modification or execution of side effects.
Documented attack patterns abuse exactly the kind of access list_user_ranges gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LudusMCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_user_ranges:
{
"version": "1",
"default": "deny",
"tools": {
"list_user_ranges": {}
}
}list_user_ranges is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all deployed ranges for a user, showing current status and basic information. It is categorised as a Read tool in the LudusMCP Server MCP Server, which means it retrieves data without modifying state.
Register the LudusMCP Server MCP server in PolicyLayer and add a rule for list_user_ranges: 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 LudusMCP Server. Nothing to install.
list_user_ranges is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_user_ranges 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 list_user_ranges. 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.
list_user_ranges is provided by the LudusMCP Server MCP server (noctedefensor/ludusmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 LudusMCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 LudusMCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.