List devices in the GLP workspace (warranty, subscription state, lifecycle).
AI agents call list_glp_devices to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation to list and query existing device metadata in the GreenLake Platform workspace. It has no capability to create, modify, delete, execute code, or commit financial transactions. The blast radius of misuse is minimal—an agent could only view device information that would typically be accessible to authenticated users of the platform.
From the tool's definition Tool name 'list_glp_devices' and description 'List devices in the GLP workspace' indicate a read-only query operation that retrieves device information (warranty, subscription state, lifecycle) with no modification or side effects.
Attacks that exploit this kind of access
List devices in the GLP workspace (warranty, subscription state, lifecycle). It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for list_glp_devices: 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.
list_glp_devices 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 list_glp_devices 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 list_glp_devices. 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.
list_glp_devices 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 →