Get range access logs. Args: user_id: Optional user ID (admin only) limit: Maximum number of log entries to return Returns: List of access log entries
AI agents call range_access_logs 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 only queries and retrieves existing log data without any side effects or modifications. It is a straightforward read operation that returns access logs. Even though it includes an admin-only parameter (user_id), the tool itself performs no destructive, write, or execute operations.
From the tool's definition Tool name is 'range_access_logs' and description states 'Get range access logs'. The function retrieves log entries with optional filtering by user_id and limit parameters.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access range_access_logs 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 range_access_logs:
{
"version": "1",
"default": "deny",
"tools": {
"range_access_logs": {}
}
}range_access_logs 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 range access logs. Args: user_id: Optional user ID (admin only) limit: Maximum number of log entries to return Returns: List of access log entries. 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 range_access_logs: 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.
range_access_logs 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 range_access_logs 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 range_access_logs. 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.
range_access_logs 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.