Get the currently active OCI profile.
AI agents call get_current_oci_profile 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 merely reads and returns the name or details of the current OCI profile in use. It has no side effects, does not execute code or commands, and does not modify any resources. It is a simple information retrieval operation, fitting the 'Read' category. The blast radius of misuse is minimal—an attacker learns which profile is active but cannot leverage this alone to compromise resources without other tools.
From the tool's definition The tool name and description indicate it 'Get the currently active OCI profile'—a pure query operation that retrieves configuration state without modifying or executing anything.
Attacks that exploit this kind of access
Get the currently active OCI profile. 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_current_oci_profile: 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_current_oci_profile 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_current_oci_profile 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_current_oci_profile. 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_current_oci_profile 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 →