netlicensing_create_shop_token
AI agents use netlicensing_create_shop_token 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.
This tool creates a shop token, which is a writable operation that generates a new credential or authorization artifact in the NetLicensing system. While the description is empty (lowering confidence slightly), the naming pattern and context as a licensing management tool indicate it creates data.
From the tool's definition Tool name 'netlicensing_create_shop_token' indicates creation of a security credential (token) in a licensing system.
Attacks that exploit this kind of access
netlicensing_create_shop_token. 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_shop_token: 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_shop_token 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_shop_token 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_shop_token. 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_shop_token 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 →