Get the current status and details of a Ludus range. Shows deployment state, VM information, and range configuration. Requires admin privileges to check other users\
AI agents call get_range_status 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 a Ludus range's current state and configuration. It has no side effects, does not create, modify, delete, or execute operations. The requirement for admin privileges to check other users' ranges is a permission control, not a functional capability that would elevate the category. The tool is purely informational.
From the tool's definition Tool description explicitly states 'Get the current status and details' and 'Shows deployment state, VM information, and range configuration' — all read operations with no modification or deletion of data.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_range_status 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 get_range_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_range_status": {}
}
}get_range_status 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.
Get the current status and details of a Ludus range. Shows deployment state, VM information, and range configuration. Requires admin privileges to check other users\. 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 get_range_status: 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.
get_range_status 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 get_range_status 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 get_range_status. 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.
get_range_status 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.