AI agents call get_history 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.
The 'get_' prefix conventionally indicates a retrieval operation with no side effects. In the context of Ignition SCADA systems, history typically refers to historical data, logs, or time-series records. Severity is medium rather than low because historical data in SCADA systems may contain sensitive operational information, process parameters, or security-relevant events that could inform attacks.
From the tool's definition Tool name 'get_history' suggests data retrieval. Description is empty, limiting direct evidence. Based on naming convention and sibling tools context (get_alarm, get_named_query, get_script, get_tags, get_udt, get_view all being Read operations), this follows…
Attacks that exploit this kind of access
get_history. 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_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 Ignition. Nothing to install.
get_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_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_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_history 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.
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 →