Add a new protective smart rule to the global node9 config (~/.node9/config.json).
AI agents use node9_rule_add to create or update resources in Node9-Proxy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Node9-Proxy environment.
This tool creates or modifies configuration data (a new rule in the global node9 config file). While the operation is reversible (rules can presumably be removed), it affects security governance policies for an autonomous agent execution platform. Misuse could weaken security controls, bypass protective measures, or alter governance rules for all agents—hence 'high' severity.
From the tool's definition Tool description states it will 'Add a new protective smart rule to the global node9 config (~/.node9/config.json)', which is a create/modify operation on a configuration file.
Documented attack patterns abuse exactly the kind of access node9_rule_add gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Node9-Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for node9_rule_add:
{
"version": "1",
"default": "deny",
"tools": {
"node9_rule_add": {
"limits": [
{
"counter": "node9_rule_add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}node9_rule_add stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a new protective smart rule to the global node9 config (~/.node9/config.json). It is categorised as a Write tool in the Node9-Proxy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Node9-Proxy MCP server in PolicyLayer and add a rule for node9_rule_add: 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 Node9-Proxy. Nothing to install.
node9_rule_add 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 node9_rule_add 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 node9_rule_add. 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.
node9_rule_add is provided by the Node9-Proxy MCP server (node9-ai/node9-proxy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Node9-Proxy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Node9-Proxy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.