List VNIC attachments (incl. public IP) for an instance.
AI agents call list_instance_vnics 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 VNIC (Virtual Network Interface Card) attachment information and associated public IPs for a given OCI instance. It is a read-only query operation that gathers existing state information without creating, modifying, deleting, or executing any actions. The blast radius is limited to information disclosure of network configuration already provisioned.
From the tool's definition Tool name 'list_instance_vnics' and description 'List VNIC attachments (incl. public IP) for an instance' indicate a query/retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
List VNIC attachments (incl. public IP) for an instance. 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_instance_vnics: 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_instance_vnics 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_instance_vnics 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_instance_vnics. 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_instance_vnics 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 →