list_compartments
AI agents call list_compartments 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.
The tool lists compartments (organizational units in OCI) with no side effects. This is a pure read operation for querying infrastructure metadata. Low severity because listing compartments reveals structure but does not expose sensitive data directly and cannot modify or delete resources. Confidence slightly reduced due to missing description, but sibling tool patterns and naming conventions are reliable indicators.
From the tool's definition Tool name 'list_compartments' indicates retrieval of compartment information. Consistent with sibling tools like 'get_alarm', 'get_bucket', 'get_budget' which are all read-only queries.
Attacks that exploit this kind of access
list_compartments. 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_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 MCP Server. 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 MCP server (jopsis/mcp-server-oci). 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 →