netlicensing_preview_update_product
AI agents use netlicensing_preview_update_product 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.
The tool name implies a write/update operation on a product entity. The 'preview' prefix may indicate this is a non-destructive preview of an update rather than the actual update, but without a description, this is uncertain. Given sibling tools follow create/delete patterns, this is likely a write operation. Confidence is reduced due to the empty description and ambiguity introduced by 'preview'.
From the tool's definition Tool name contains 'update_product' suggesting modification of product data; description is empty and uninformative.
Attacks that exploit this kind of access
netlicensing_preview_update_product. 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_preview_update_product: 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_preview_update_product 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_preview_update_product 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_preview_update_product. 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_preview_update_product 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 →