AI agents call list_scripts 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 lists metadata about scripts (their names and scope) without executing them, modifying them, or causing side effects. It is a read-only operation analogous to 'list' or 'get' operations. While it exposes information about available scripts in an Ignition project, which could be reconnaissance useful to an attacker, the tool itself performs no destructive, financial, or executable actions.
From the tool's definition Tool name 'list_scripts' and description 'List all scripts in an Ignition project with their scope' indicate retrieval/enumeration of existing data without modification or execution.
Attacks that exploit this kind of access
List all scripts in an Ignition project with their scope. 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_scripts: 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_scripts 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_scripts 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_scripts. 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_scripts 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 →