ROLES DOCUMENTATION - Direct Access to Complete Ludus Roles Documentation DIRECT ACCESS TO: - Complete roles listing and descriptions - Role variables and configuration options - Role dependencies and requirements - GitHub repositories and sources - Installation and usage examples SIMPLIFIED FUNC...
AI agents call ludus_roles_docs_read 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 exclusively reads and retrieves documentation about available roles in the Ludus training environment. It has no side effects, does not modify any data, does not execute operations, and does not delete anything. It is a pure information retrieval tool used for planning and research during range configuration.
From the tool's definition Tool description states it "Direct Access to Complete Ludus Roles Documentation" and "returns the complete roles documentation (docs/roles.md)" with "No search filtering - reads entire document".
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access ludus_roles_docs_read 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 ludus_roles_docs_read:
{
"version": "1",
"default": "deny",
"tools": {
"ludus_roles_docs_read": {}
}
}ludus_roles_docs_read 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.
ROLES DOCUMENTATION - Direct Access to Complete Ludus Roles Documentation DIRECT ACCESS TO: - Complete roles listing and descriptions - Role variables and configuration options - Role dependencies and requirements - GitHub repositories and sources - Installation and usage examples SIMPLIFIED FUNCTIONALITY: - Always returns the complete roles documentation (docs/roles.md) - No search filtering - reads entire document - Immediate access to all role information PERFECT FOR: - Range planning (ludus_range_planner step 3) - Role research and selection - Finding role variables and GitHub links - Understanding role capabilities TARGET: Focuses specifically on \. 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 ludus_roles_docs_read: 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.
ludus_roles_docs_read 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 ludus_roles_docs_read 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 ludus_roles_docs_read. 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.
ludus_roles_docs_read 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.