Get current user's range information. Args: user_id: Optional user ID (admin only) Returns: Range information
AI agents call get_range to retrieve information from Ludus FastMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves range information for the current user or optionally another user (with admin privileges). It is a read-only operation that queries existing data without creating, modifying, deleting, or executing operations. The blast radius is minimal—misuse would only expose range configuration details that an admin could already access. Classification as Read is appropriate.
From the tool's definition Tool name 'get_range' and description 'Get current user's range information' indicates retrieval of data with no side effects. The optional user_id parameter (admin only) is a query filter, not a destructive or modifying operation.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_range 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 get_range:
{
"version": "1",
"default": "deny",
"tools": {
"get_range": {}
}
}get_range 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 current user's range information. Args: user_id: Optional user ID (admin only) Returns: Range information. It is categorised as a Read tool in the Ludus FastMCP MCP Server, which means it retrieves data without modifying state.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for get_range: 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.
get_range 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 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. 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 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.