Delete a blueprint. Args: blueprint_id: ID of the blueprint to delete Returns: Deletion confirmation
AI agents call delete_blueprint to permanently remove resources in Ludus FastMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a blueprint, which cannot be undone. Blueprints in a cyber range management system are likely templates or configurations used for deploying scenarios. Deletion is irreversible and has high blast radius if an agent mistakenly deletes critical or in-use blueprints. This clearly qualifies as Destructive rather than Write (which would be reversible modifications).
From the tool's definition Tool name is 'delete_blueprint' and description explicitly states 'Delete a blueprint' with 'Deletion confirmation' as return value. The term 'delete' unambiguously indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_blueprint 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 delete_blueprint:
{
"version": "1",
"default": "deny",
"hide": [
"delete_blueprint"
]
}delete_blueprint disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a blueprint. Args: blueprint_id: ID of the blueprint to delete Returns: Deletion confirmation. It is categorised as a Destructive tool in the Ludus FastMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for delete_blueprint: 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.
delete_blueprint is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_blueprint 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 delete_blueprint. 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.
delete_blueprint 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.