AI agents call get_view 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 the structure of a Perspective view (component tree, bindings, configuration). It performs read-only operations with no side effects on the system. While it may expose sensitive structural information about views, the tool itself cannot modify, delete, or execute anything. This is a classic Read category operation.
From the tool's definition Tool name is 'get_view' and description states 'Get a Perspective view's component tree, bindings, and structure' — uses the verb 'Get' indicating retrieval without modification.
Attacks that exploit this kind of access
Get a Perspective view's component tree, bindings, and structure. 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_view: 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_view 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_view 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_view. 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_view 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 →