list_glp_virtual_machines
List virtual machines managed via the GLP Virtualization service.
This record as markdown: /tools/secure-ssid-centralmcp/list-glp-virtual-machines.md
What list_glp_virtual_machines does on API-Central
AI agents call list_glp_virtual_machines to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_glp_virtual_machines is rated Low
This tool performs a data retrieval operation with no side effects. Listing VMs is a monitoring/querying function that does not create, modify, delete, or execute any changes to infrastructure. The blast radius of misuse is minimal—an AI agent could only enumerate virtual machine inventory, not alter it.
From the tool's definition Tool name 'list_glp_virtual_machines' uses the verb 'list', which retrieves data about virtual machines without modification. Description states it lists VMs 'managed via the GLP Virtualization service', indicating a read-only query operation.
Attacks that exploit this kind of access
The rule that runs list_glp_virtual_machines safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_glp_virtual_machines, this is the rule to start with:
list_glp_virtual_machines is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every list_glp_virtual_machines call is checked against it from then on.
Questions about list_glp_virtual_machines
List virtual machines managed via the GLP Virtualization service. 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_virtual_machines: 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_virtual_machines 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_virtual_machines 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_virtual_machines. 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_virtual_machines 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.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue