list_keys
AI agents call list_keys 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 name 'list_keys' indicates retrieval of cryptographic or access keys in OCI. This is a Read operation as it queries and returns existing key material without modifying it. Severity is medium rather than low because exposure of key listings could help an attacker identify targets for further compromise, though the tool itself does not create, modify, or delete keys.
From the tool's definition Tool name 'list_keys' combined with sibling tools that are primarily Read operations (get_alarm, get_autonomous_database, get_boot_volume, get_bucket, etc.). The 'list_' prefix conventionally retrieves/enumerates resources without modification.
Attacks that exploit this kind of access
list_keys. 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_keys: 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_keys 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_keys 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_keys. 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_keys 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 →