AI agents call get_bucket 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 only queries and retrieves information about a storage bucket's configuration. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. It is a straightforward read operation with minimal security impact, appropriate for informational purposes only.
From the tool's definition Tool retrieves bucket metadata (storage tier, versioning, replication, access type) without modifying or deleting any resources. The verb 'get' and description indicate read-only access to object storage metadata.
Attacks that exploit this kind of access
Get metadata for a specific bucket: storage tier, versioning, replication, access type. 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 get_bucket: 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.
get_bucket 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 get_bucket 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 get_bucket. 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.
get_bucket is provided by the Oci MCP server (sauryadas/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 →