Get help information for Ludus CLI commands and subcommands.
AI agents call ludus_help 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 and displays help documentation for CLI commands. It is purely informational, performs no modifications or deletions, executes no external operations, and creates no financial obligations. It is a standard Read operation with minimal risk, as help text cannot cause harm when retrieved by an AI agent.
From the tool's definition Tool name 'ludus_help' and description 'Get help information for Ludus CLI commands and subcommands' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access ludus_help 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_help:
{
"version": "1",
"default": "deny",
"tools": {
"ludus_help": {}
}
}ludus_help 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 help information for Ludus CLI commands and subcommands. 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_help: 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_help 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_help 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_help. 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_help 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.