List all your Verda Cloud instances with their status.
AI agents call list_instances to retrieve information from Verda Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing instance metadata and status. It has no side effects, does not execute operations, and does not modify or delete any infrastructure. It is a pure read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_instances' and description 'List all your Verda Cloud instances with their status' indicate a query operation that retrieves information without modifying or deleting any resources.
Attacks that exploit this kind of access
List all your Verda Cloud instances with their status. It is categorised as a Read tool in the Verda Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Verda Cloud MCP Server MCP server in PolicyLayer and add a rule for list_instances: 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 Verda Cloud MCP Server. Nothing to install.
list_instances 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_instances 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_instances. 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_instances is provided by the Verda Cloud MCP Server MCP server (sniper35/verda-cloud-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 →