AI agents call list_compartments 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.
The tool performs a query/list operation to retrieve compartment metadata. There are no side effects, no data modification, no code execution, and no financial implications. It simply enumerates existing compartments in the Oracle Cloud tenancy hierarchy, making it a straightforward Read category tool with low severity.
From the tool's definition Tool name is 'list_compartments' and description states 'List accessible compartments in the tenancy (including subtrees)' — this is a read-only operation that retrieves organizational structure information without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
List accessible compartments in the tenancy (including subtrees). 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_compartments: 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_compartments 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_compartments 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_compartments. 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_compartments 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 →