netlicensing_create_bundle
AI agents use netlicensing_create_bundle to create or update resources in Labs64/NetLicensing — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Labs64/NetLicensing environment.
The 'create_bundle' operation creates new licensing entities within NetLicensing. While the description is empty, the tool name clearly indicates data creation. This is reversible (bundles can be deleted, as evidenced by the sibling 'netlicensing_delete_bundle' tool), so it classifies as Write rather than Destructive.
From the tool's definition Tool name 'netlicensing_create_bundle' indicates a create operation within a licensing management system. Sibling tools include create_license, create_licensee, create_product, and delete operations, establishing context as a licensing platform with…
Attacks that exploit this kind of access
netlicensing_create_bundle. It is categorised as a Write tool in the Labs64/NetLicensing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Labs64/NetLicensing MCP server in PolicyLayer and add a rule for netlicensing_create_bundle: 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_create_bundle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the netlicensing_create_bundle 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_create_bundle. 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_create_bundle 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 →