Import a scenario from the community repository. Args: scenario_url: URL to community scenario user_id: Optional user ID (admin only) Returns: Import result with scenario information
AI agents use import_community_scenario to create or update resources in Ludus FastMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ludus FastMCP environment.
Importing a scenario is a reversible modification that adds new configuration or test data to the cyber range environment. While it creates data (Write category) rather than merely reading it, it is not destructive since imports can be removed.
From the tool's definition The tool imports a scenario from a community repository, which creates new scenario data in the system. The description explicitly states it returns an 'Import result with scenario information', indicating data is being added/created in the Ludus environment.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access import_community_scenario 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 import_community_scenario:
{
"version": "1",
"default": "deny",
"tools": {
"import_community_scenario": {
"limits": [
{
"counter": "import_community_scenario_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_community_scenario stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Import a scenario from the community repository. Args: scenario_url: URL to community scenario user_id: Optional user ID (admin only) Returns: Import result with scenario information. It is categorised as a Write tool in the Ludus FastMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for import_community_scenario: 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.
import_community_scenario is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_community_scenario 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 import_community_scenario. 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.
import_community_scenario 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.