infomaniak_nodejs_app_action
Start, stop, restart, or build a Node.js application. Two-phase commit: first call returns a plan + token, second call (with the token + same args) applies.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-nodejs-app-action.md
What infomaniak_nodejs_app_action does on Infomaniak Admin
AI agents invoke infomaniak_nodejs_app_action to trigger actions in Infomaniak Admin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why infomaniak_nodejs_app_action is rated High
This tool executes commands that control application lifecycle and trigger code builds, which are Execute-category operations. While the two-phase commit pattern mitigates accidental misuse, an agent with malicious intent could restart applications to cause denial of service, stop critical services, or execute arbitrary build processes (depending on build script contents).
From the tool's definition Tool performs 'Start, stop, restart, or build a Node.js application' — these are external operations that trigger application state changes and runtime behaviors. 'Build' in particular executes code compilation/deployment logic.
Attacks that exploit this kind of access
The rule that runs infomaniak_nodejs_app_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Infomaniak Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infomaniak_nodejs_app_action, this is the rule to start with:
infomaniak_nodejs_app_action stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_nodejs_app_action call is checked against it from then on.
Questions about infomaniak_nodejs_app_action
Start, stop, restart, or build a Node.js application. Two-phase commit: first call returns a plan + token, second call (with the token + same args) applies. It is categorised as a Execute tool in the Infomaniak Admin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_nodejs_app_action: 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 Infomaniak Admin. Nothing to install.
infomaniak_nodejs_app_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the infomaniak_nodejs_app_action 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 infomaniak_nodejs_app_action. 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.
infomaniak_nodejs_app_action is provided by the Infomaniak Admin MCP server (henrikogaard/infomaniak-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Infomaniak Admin, and thousands of servers like it.
Across the catalogue