List public/private Load Balancers.
AI agents call list_load_balancers 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.
This is a read-only operation that enumerates load balancers in an OCI tenancy. It retrieves data about existing resources but does not create, modify, delete, or execute operations. The blast radius is low—misuse would expose infrastructure details but not directly impact availability or security unless the information is used for further attacks. Classified as Read with low severity.
From the tool's definition Tool name 'list_load_balancers' and description 'List public/private Load Balancers' indicate a retrieval operation that queries existing load balancer configurations without modification.
Attacks that exploit this kind of access
List public/private Load Balancers. 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_load_balancers: 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_load_balancers 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_load_balancers 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_load_balancers. 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_load_balancers is provided by the OCI MCP Server MCP server (sarthak-pansare/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 →