netlicensing_delete_license_template
AI agents call netlicensing_delete_license_template to permanently remove resources in Labs64/NetLicensing — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' prefix in the tool name indicates this performs an irreversible destructive action. License templates are core licensing infrastructure; deleting them would permanently remove template records that other licenses or licensees may depend on, causing cascading effects.
From the tool's definition Tool name contains 'delete' which indicates irreversible data removal. Server context involves managing licensing lifecycle including templates.
Attacks that exploit this kind of access
netlicensing_delete_license_template. It is categorised as a Destructive tool in the Labs64/NetLicensing MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Labs64/NetLicensing MCP server in PolicyLayer and add a rule for netlicensing_delete_license_template: 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 Labs64/NetLicensing. Nothing to install.
netlicensing_delete_license_template 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 netlicensing_delete_license_template 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 netlicensing_delete_license_template. 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.
netlicensing_delete_license_template is provided by the Labs64/NetLicensing MCP server (labs64/netlicensing-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →