List service gateways (private access to OCI services).
AI agents call list_service_gateways 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 tool retrieves and displays information about existing service gateways in OCI. It performs no data modification, code execution, or destructive actions. The blast radius of misuse is minimal—an LLM agent querying service gateway configurations poses no direct operational risk beyond potential information disclosure, which is typical of read operations.
From the tool's definition Tool name 'list_service_gateways' and description 'List service gateways' indicate a retrieval/query operation with no modification or execution of external systems.
Attacks that exploit this kind of access
List service gateways (private access to OCI services). 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_service_gateways: 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_service_gateways 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_service_gateways 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_service_gateways. 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_service_gateways 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 →