Get details of a specific license.
AI agents call netlicensing_get_license 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.
This tool retrieves license information without creating, modifying, deleting, or executing any operations. It is a straightforward data query operation. The low severity reflects that reading license details poses minimal risk even if misused by an agent, as it only exposes existing data without altering system state or enabling financial transactions.
From the tool's definition Tool name contains 'get' and description states 'Get details of a specific license' - a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific license. 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_get_license: 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_get_license 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_get_license 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_get_license. 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_get_license 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 →