get_alarm_history
AI agents call get_alarm_history 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 historical alarm data from OCI monitoring/alerting systems. Fetching alarm history is a read operation with no side effects—it does not modify, delete, execute code, or commit financial transactions. The naming pattern and server context confirm this is a data query operation.
From the tool's definition Tool name 'get_alarm_history' indicates retrieval of alarm history data. The empty description is uninformative, but the 'get_' prefix and sibling tools (get_alarm, get_autonomous_database, get_boot_volume, get_bucket, get_budget, etc.) all follow a pattern…
Attacks that exploit this kind of access
get_alarm_history. 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_alarm_history: 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_alarm_history 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_alarm_history 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_alarm_history. 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_alarm_history 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 →