list_subnets
AI agents call list_subnets 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.
Listing subnets is a read operation that queries and enumerates network configuration data. The tool retrieves existing resource information with no side effects. Severity is medium rather than low because exposure of subnet architecture and network topology to an untrusted agent could inform lateral movement or reconnaissance attacks, though it does not directly enable destructive actions.
From the tool's definition Tool name 'list_subnets' indicates a listing/retrieval operation. The prefix 'list_' is a strong semantic indicator of a read-only enumeration of resources, consistent with sibling tools like 'get_alarm', 'get_bucket', 'get_cost_by_compartment' which are all…
Attacks that exploit this kind of access
list_subnets. 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_subnets: 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_subnets 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_subnets 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_subnets. 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_subnets 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 →