netlicensing_obtain_bundle
AI agents call netlicensing_obtain_bundle to retrieve information from Labs64/NetLicensing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'obtain_bundle' most naturally indicates a retrieval operation to fetch or query bundle data from the NetLicensing system. Without a descriptive field, we infer from naming convention that 'obtain' (paired with 'bundle') is a Read operation.
From the tool's definition Tool name 'obtain_bundle' suggests retrieval of bundle information; the verb 'obtain' is consistent with data retrieval rather than modification or deletion. However, the description is empty, limiting confidence.
Attacks that exploit this kind of access
netlicensing_obtain_bundle. It is categorised as a Read tool in the Labs64/NetLicensing MCP Server, which means it retrieves data without modifying state.
Register the Labs64/NetLicensing MCP server in PolicyLayer and add a rule for netlicensing_obtain_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_obtain_bundle is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the netlicensing_obtain_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_obtain_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_obtain_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 →