List metric definitions in a compartment. namespace e.g. oci_computeagent.
AI agents call list_metrics 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 metric definitions from OCI's monitoring service without creating, modifying, deleting, or executing any operations. It has no side effects and returns informational data only. The blast radius of misuse is minimal—an attacker could discover what metrics exist but cannot alter infrastructure or access sensitive data beyond metric metadata.
From the tool's definition Tool name 'list_metrics' and description 'List metric definitions in a compartment' indicate a retrieval operation with no modification or execution of operations. The action is querying metric definitions, which is a read-only operation.
Attacks that exploit this kind of access
List metric definitions in a compartment. namespace e.g. oci_computeagent. 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_metrics: 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_metrics 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_metrics 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_metrics. 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_metrics 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 →