AI agents call list_tag_providers 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 queries and returns metadata about Ignition tag providers without creating, modifying, or deleting any data. It has no side effects and poses minimal risk even if misused by an AI agent — the worst outcome is enumeration of existing provider names. The low blast radius and read-only nature confirm the Read category with high confidence.
From the tool's definition Tool description states 'List all tag provider names' — a retrieval operation with no modification capability. The verb 'list' is a classic read-only action, consistent with the sibling tools list_alarms and list_named_queries.
Attacks that exploit this kind of access
List all tag provider names in an Ignition project (e.g. 'default', 'edge'). 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 list_tag_providers: 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.
list_tag_providers 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_tag_providers 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_tag_providers. 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_tag_providers 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 →