Test network connectivity between VMs. Args: source_vm: Source VM name target_vm: Target VM name protocol: Protocol to test (tcp, udp, icmp) port: Optional port number for tcp/udp user_id: Optional user ID (admin only) Returns: Connectivity test result
AI agents invoke test_network_connectivity to trigger actions in Ludus FastMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool actively runs network connectivity tests (ping, port scans, or similar probes) between VMs in a cyber range environment. It triggers external operations whose effects depend on arguments (source VM, target VM, protocol, port). This is Execute rather than Read because it actively sends network traffic/probes rather than simply querying stored data.
From the tool's definition Test network connectivity between VMs... Protocol to test (tcp, udp, icmp)... Optional port number for tcp/udp
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access test_network_connectivity 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 test_network_connectivity:
{
"version": "1",
"default": "deny",
"tools": {
"test_network_connectivity": {
"limits": [
{
"counter": "test_network_connectivity_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} test_network_connectivity stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Test network connectivity between VMs. Args: source_vm: Source VM name target_vm: Target VM name protocol: Protocol to test (tcp, udp, icmp) port: Optional port number for tcp/udp user_id: Optional user ID (admin only) Returns: Connectivity test result. It is categorised as a Execute tool in the Ludus FastMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for test_network_connectivity: 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.
test_network_connectivity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_network_connectivity 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 test_network_connectivity. 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.
test_network_connectivity 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.