build_container_based_template

What build_container_based_template does on Ludus FastMCP

AI agents invoke build_container_based_template 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.

Why build_container_based_template is rated High

Building a container template is an Execute action—it triggers compilation/containerization whose effects depend on build inputs and could create unintended artifacts or configurations. The empty description lowers confidence from 0.85 to 0.75, but the name and server context (template creation, scenario deployment) clearly indicate code/configuration execution rather than simple data retrieval or modification.

From the tool's definition Tool name 'build_container_based_template' suggests compiling/building container artifacts. Server context shows this is a cyber range management system with template creation capabilities. The prefix 'build_' indicates execution of a build process.

The rule that runs build_container_based_template safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_container_based_template, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "build_container_based_template": {
      "limits": [
        {
          "counter": "build_container_based_template_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about build_container_based_template