This record as markdown: /tools/tjnull-ludus-fastmcp/list-hosts.md
What list_hosts does on Ludus FastMCP
AI agents call list_hosts to retrieve information from Ludus FastMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_hosts is rated Low
This tool retrieves and displays hosts within a cyber range environment. It performs no modifications, deletions, or external operations—purely informational. The blast radius of misuse is minimal; an attacker could enumerate hosts but cannot affect range state or external systems. Confidence is high because the intent is unambiguous from both name and description.
From the tool's definition Tool name 'list_hosts' and description 'List all hosts in range' indicate a retrieval operation with no side effects. The verb 'list' is a classic Read operation that queries existing data.
Attacks that exploit this kind of access
The rule that runs list_hosts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_hosts, this is the rule to start with:
list_hosts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ludus FastMCP, apply this rule, and every list_hosts call is checked against it from then on.
Questions about list_hosts
List all hosts in range. 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 list_hosts: 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.
list_hosts 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 list_hosts 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 list_hosts. 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.
list_hosts 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.
More on Ludus Fast, and thousands of servers like it.
This server
Across the catalogue