Search Ludus roles documentation for specific roles, variables, and usage examples.
AI agents call ludus_roles_search 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.
The tool retrieves information from documentation without modifying, deleting, or executing operations. It is purely informational in nature, similar to querying a help system or knowledge base. The blast radius of misuse is minimal—worst case an agent retrieves irrelevant documentation snippets.
From the tool's definition Tool name contains 'search' and description explicitly states it 'Search[es] Ludus roles documentation for specific roles, variables, and usage examples.' This is a documentation lookup operation with no side effects.
Documented attack patterns abuse exactly the kind of access ludus_roles_search 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_search:
{
"version": "1",
"default": "deny",
"tools": {
"ludus_roles_search": {}
}
}ludus_roles_search 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.
Search Ludus roles documentation for specific roles, variables, and usage examples. 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_search: 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_search 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_search 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_search. 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_search 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.