AI agents call get_oke_cluster 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 OKE cluster configuration and metadata without modifying or deleting resources. It falls squarely into the Read category. Severity is medium because cluster endpoint configs and topology details could inform attack planning, but the tool itself has no direct destructive capability.
From the tool's definition Tool name and description indicate retrieval of cluster details: "Get full details for an OKE cluster including endpoint config, add-ons, and node pool summary." No modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
Get full details for an OKE cluster including endpoint config, add-ons, and node pool summary. 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_oke_cluster: 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_oke_cluster 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_oke_cluster 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_oke_cluster. 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_oke_cluster 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 →