netlicensing_list_licensees
AI agents call netlicensing_list_licensees 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's function is to query and enumerate licensees in the NetLicensing system. The 'list' verb indicates a retrieval operation with no capability to modify, delete, or execute actions. This is consistent with Read category operations. Confidence is slightly reduced due to empty description, but the tool name is sufficiently clear to categorize with high confidence.
From the tool's definition Tool name 'netlicensing_list_licensees' contains the verb 'list', which is a read-only operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
netlicensing_list_licensees. 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_list_licensees: 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_list_licensees 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_list_licensees 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_list_licensees. 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_list_licensees 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 →