Generate attack path documentation for a scenario. Args: scenario_key: Optional scenario key (defaults to current deployment) user_id: Optional user ID (admin only) Returns: Attack path documentation with techniques and mitigations
AI agents call get_attack_path_documentation 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.
This tool retrieves or generates documentation about attack paths, techniques, and mitigations. It reads scenario data and returns informational content without modifying system state, executing code, or having destructive effects. The optional parameters (scenario_key, user_id) are for filtering which documentation to retrieve, not for triggering changes.
From the tool's definition The tool description states it "Generate[s] attack path documentation for a scenario" and "Returns: Attack path documentation with techniques and mitigations." The verb "generate" in this context means "produce" or "retrieve" documentation, with no capability…
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_attack_path_documentation 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_attack_path_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"get_attack_path_documentation": {}
}
}get_attack_path_documentation 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.
Generate attack path documentation for a scenario. Args: scenario_key: Optional scenario key (defaults to current deployment) user_id: Optional user ID (admin only) Returns: Attack path documentation with techniques and mitigations. 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_attack_path_documentation: 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_attack_path_documentation 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_attack_path_documentation 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_attack_path_documentation. 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_attack_path_documentation 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.