List compute instances.
AI agents call list_instances to retrieve information from OCI 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 information about existing compute instances in OCI. It performs a query operation with no capability to create, modify, or delete infrastructure. The blast radius of an AI agent misusing this tool is minimal—it can only enumerate instances, not change them. Severity is low as listing resources poses no direct risk to system integrity, data security, or financial impact.
From the tool's definition Tool is named 'list_instances' and described as 'List compute instances.' The verb 'list' is explicitly a read-only operation that queries and retrieves data without modification, deletion, or side effects.
Attacks that exploit this kind of access
List compute instances. It is categorised as a Read tool in the OCI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OCI 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 OCI 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 OCI MCP Server MCP server (sarthak-pansare/oci-mcp-server). 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 →