infomaniak_nodejs_app_jobs
List the recent jobs that ran for a Node.js app (builds, restarts, etc.) with their status and a JWT-protected log_stream endpoint per job. Manager-private.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-nodejs-app-jobs.md
What infomaniak_nodejs_app_jobs does on Infomaniak Admin
AI agents call infomaniak_nodejs_app_jobs to retrieve information from Infomaniak Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why infomaniak_nodejs_app_jobs is rated Low
This tool performs a read-only operation—listing historical job data and logs for a Node.js application. No data is created, modified, deleted, or financial operations are triggered. The most severe potential misuse would be information disclosure of job logs, which is a read-level risk. Confidence is high because the function is clearly descriptive of a query/list operation.
From the tool's definition Tool 'infomaniak_nodejs_app_jobs' lists recent jobs and their status with a log_stream endpoint. The verb 'list' and description of retrieving job history and status indicates retrieval of existing data without modification.
Attacks that exploit this kind of access
The rule that runs infomaniak_nodejs_app_jobs 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_jobs, this is the rule to start with:
infomaniak_nodejs_app_jobs is read-only, so it stays allowed. 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_jobs call is checked against it from then on.
Questions about infomaniak_nodejs_app_jobs
List the recent jobs that ran for a Node.js app (builds, restarts, etc.) with their status and a JWT-protected log_stream endpoint per job. Manager-private. It is categorised as a Read tool in the Infomaniak Admin MCP Server, which means it retrieves data without modifying state.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_nodejs_app_jobs: 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_jobs 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 infomaniak_nodejs_app_jobs 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_jobs. 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_jobs 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.
This server
Across the catalogue