get_load_balancer
AI agents call get_load_balancer 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 retrieves load balancer configuration or status information from OCI. No description is provided, but the naming convention and context among sibling read-only tools strongly indicate this is a query/retrieval operation. Load balancer 'get' operations typically return metadata and state without modifying resources.
From the tool's definition Tool name 'get_load_balancer' follows the 'get_*' pattern consistent with other read-only retrieval tools on this server (get_alarm, get_autonomous_database, get_boot_volume, get_bucket, get_budget, get_cost_by_compartment, etc.).
Attacks that exploit this kind of access
get_load_balancer. 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 get_load_balancer: 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.
get_load_balancer 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_load_balancer 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_load_balancer. 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_load_balancer 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 →