AI agents call get_alarm to retrieve information from Ignition without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries alarm pipeline configuration data (stages, notifications, transitions) without creating, modifying, or deleting any state. It is a straightforward data retrieval operation analogous to the Read category tools in the sibling set (get_history, get_named_query, get_script, get_tags, get_udt, get_view). No side effects or data modification occur.
From the tool's definition Tool name 'get_alarm' and description 'Get an alarm pipeline's configuration' — the verb 'Get' and the action of retrieving configuration are read-only operations with no side effects.
Attacks that exploit this kind of access
Get an alarm pipeline's configuration including stages, notifications, and transitions. It is categorised as a Read tool in the Ignition MCP Server, which means it retrieves data without modifying state.
Register the Ignition MCP server in PolicyLayer and add a rule for get_alarm: 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 Ignition. Nothing to install.
get_alarm 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 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. 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 is provided by the Ignition MCP server (nodeblue-ai/ignition-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_alarm is one line of Ignition's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →