AI agents call get-settings to retrieve information from Node Red without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a getter function that reads settings without modifying or executing anything. While the description is empty, the naming convention and context strongly suggest a read-only query operation. Settings retrieval may expose configuration details, which warrants 'low' severity due to potential information disclosure, but there is no destructive, financial, or execution component.
From the tool's definition Tool name 'get-settings' indicates a retrieval operation that fetches configuration or state information. The name structure parallels other Read tools on this server (get-diagnostics, get-flow, get-flows, get-flows-state, get-node-info), all of which…
Attacks that exploit this kind of access
get-settings. It is categorised as a Read tool in the Node Red MCP Server, which means it retrieves data without modifying state.
Register the Node Red MCP server in PolicyLayer and add a rule for get-settings: 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 Node Red. Nothing to install.
get-settings 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-settings 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-settings. 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-settings is provided by the Node Red MCP server (node-red-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 →