submit_job

Submit job to Nomad cluster

SERVERNcp SOURCE@portel/ncp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/submit-job.md

WHAT IT DOES

What submit_job does on Ncp

AI agents invoke submit_job to trigger actions in Ncp. 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.

RISK

Why submit_job is rated High

Submitting a job to Nomad causes the cluster to schedule and run workloads (containers, binaries, etc.). This is an Execute-category action because it triggers external operations whose effects depend on the job specification provided. Severity is high because a misused job submission could run arbitrary workloads, consume cluster resources, or cause cascading failures across the infrastructure.

From the tool's definition 'Submit job to Nomad cluster' — submitting a job triggers external execution of workloads on a Nomad cluster

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs submit_job safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For submit_job, this is the rule to start with:

submit_job Rate-limited

submit_job 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_job": {
      "limits": [
        {
          "counter": "submit_job_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every submit_job call is checked against it from then on.

FAQ

Questions about submit_job

What does the submit_job tool do? +

Submit job to Nomad cluster. It is categorised as a Execute tool in the Ncp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on submit_job? +

Register the Ncp MCP server in PolicyLayer and add a rule for submit_job: 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 Ncp. Nothing to install.

What risk level is submit_job? +

submit_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit submit_job? +

Yes. Add a rate_limit block to the submit_job 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.

How do I block submit_job completely? +

Set action: deny in the PolicyLayer policy for submit_job. 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.

What MCP server provides submit_job? +

submit_job is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →