Get template build logs. Args: template_id: Template ID user_id: Optional user ID (admin only) Returns: Template build logs
AI agents call get_template_logs 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 diagnostic logs without creating, modifying, or deleting any data. It is a pure read operation that queries existing template build logs. Even with admin-only user_id filtering, the function remains informational and has no side effects on the cyber range environment.
From the tool's definition Tool name 'get_template_logs' and description 'Get template build logs' indicate a retrieval operation. The return value is 'Template build logs', which is read-only diagnostic information.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_template_logs 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_template_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_template_logs": {}
}
}get_template_logs 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 template build logs. Args: template_id: Template ID user_id: Optional user ID (admin only) Returns: Template build logs. 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_template_logs: 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_template_logs 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_template_logs 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_template_logs. 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_template_logs 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.