AI agents call get_required_roles_for_scenario to retrieve information from Ludus FastMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'get' combined with 'required_roles' indicates this tool queries or retrieves information about roles needed for a scenario. There are no indicators (create, delete, execute, etc.) suggesting modification, execution, or destructive capability. Even in the context of a cyber range management system, retrieving role requirements is a read-only operation.
From the tool's definition Tool name 'get_required_roles_for_scenario' uses the verb 'get', which indicates retrieval/query operation without side effects. The empty description limits certainty, but the naming convention strongly suggests a lookup or information retrieval function.
Documented attack patterns abuse exactly the kind of access get_required_roles_for_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 get_required_roles_for_scenario:
{
"version": "1",
"default": "deny",
"tools": {
"get_required_roles_for_scenario": {}
}
}get_required_roles_for_scenario 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_required_roles_for_scenario. 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 get_required_roles_for_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.
get_required_roles_for_scenario 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 get_required_roles_for_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 get_required_roles_for_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.
get_required_roles_for_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.