netlicensing_update_bundle · Labs64/NetLicensing MCP

WHAT IT DOES

What netlicensing_update_bundle does on Labs64/NetLicensing

AI agents use netlicensing_update_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.

WHY IT NEEDS A POLICY

Why netlicensing_update_bundle needs a policy

This tool modifies existing licensing bundles within the NetLicensing system. Updates are reversible operations, making this a Write-category tool rather than Destructive. The medium severity reflects potential business impact (bundle configurations affect software licensing), but the reversible nature and lack of financial transaction indicates it is not high-severity.

From the tool's definition Tool name 'netlicensing_update_bundle' indicates modification of bundle data. Sibling tools include 'netlicensing_create_bundle' and 'netlicensing_delete_bundle', establishing this as part of a data management suite.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

netlicensing_update_bundle Rate-limited

netlicensing_update_bundle stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "netlicensing_update_bundle": {
      "limits": [
        {
          "counter": "netlicensing_update_bundle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Labs64/NetLicensing, so you can run agents against it safely.

FAQ

Questions about netlicensing_update_bundle

What does the netlicensing_update_bundle tool do? +

netlicensing_update_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.

How do I enforce a policy on netlicensing_update_bundle? +

Register the Labs64/NetLicensing MCP server in PolicyLayer and add a rule for netlicensing_update_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.

What risk level is netlicensing_update_bundle? +

netlicensing_update_bundle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit netlicensing_update_bundle? +

Yes. Add a rate_limit block to the netlicensing_update_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.

How do I block netlicensing_update_bundle completely? +

Set action: deny in the PolicyLayer policy for netlicensing_update_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.

What MCP server provides netlicensing_update_bundle? +

netlicensing_update_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.