Assign a GLP subscription (license) to a device.
AI agents use glp_assign_subscription to create or update resources in API-Central — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.
This tool creates or modifies subscription/licensing assignments, which is a reversible write operation. While it affects financial/licensing infrastructure (GreenLake Platform), the primary action is assignment/modification of a license entitlement rather than financial transaction execution.
From the tool's definition Tool name 'glp_assign_subscription' and description 'Assign a GLP subscription (license) to a device' indicates modification of licensing/subscription state on a device.
Attacks that exploit this kind of access
Assign a GLP subscription (license) to a device. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the API-Central MCP server in PolicyLayer and add a rule for glp_assign_subscription: 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 API-Central. Nothing to install.
glp_assign_subscription 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 glp_assign_subscription 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 glp_assign_subscription. 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.
glp_assign_subscription is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →