AI agents call list_compute_instances to retrieve information from Oci without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data about OCI Compute instances without creating, modifying, deleting, or executing any actions. It is purely informational and has no capability to change infrastructure state or trigger external operations. The blast radius of misuse is minimal—an attacker gains visibility into instance inventory but cannot perform actions on those instances.
From the tool's definition Tool name 'list_compute_instances' and description 'List Compute instances' indicates a retrieval/query operation with no side effects. The verb 'list' is a classic read-only action that returns information about existing resources.
Attacks that exploit this kind of access
List Compute instances. It is categorised as a Read tool in the Oci MCP Server, which means it retrieves data without modifying state.
Register the Oci MCP server in PolicyLayer and add a rule for list_compute_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. Nothing to install.
list_compute_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_compute_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_compute_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_compute_instances is provided by the Oci MCP server (oreo-tech/oci-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 →