AI agents use write_tag to create or update resources in Ignition — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ignition environment.
This tool creates or modifies data (tag values in a SCADA system) reversibly. While the description is empty, the name 'write_tag' combined with context (Ignition SCADA platform where tags represent real-time data and control points) clearly indicates Write capability.
From the tool's definition Tool named 'write_tag' on an Ignition SCADA server. 'Write' in the name indicates modification of tag values. SCADA systems control industrial/critical infrastructure; writing tags can alter system state, sensor readings, or control outputs.
Attacks that exploit this kind of access
write_tag. It is categorised as a Write tool in the Ignition MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ignition MCP server in PolicyLayer and add a rule for write_tag: 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.
write_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the write_tag 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 write_tag. 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.
write_tag 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 →