submit_job · Cardzero MCP: Risk & Policy

WHAT IT DOES

What submit_job does on Cardzero

AI agents invoke submit_job to trigger actions in Cardzero. 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 IT NEEDS A POLICY

Why submit_job needs a policy

This tool triggers an on-chain transaction (smart contract interaction) to post a deliverable hash, changing the job's state from 'funded' to 'submitted'. It executes an external blockchain operation with real-world consequences tied to financial escrow.

From the tool's definition Posts the deliverable hash on-chain; Evaluator then auto-approves or rejects. Status: funded → submitted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cardzero, so you can run agents against it safely.

FAQ

Questions about submit_job

What does the submit_job tool do? +

Submit a deliverable for a Job (Provider side). Posts the deliverable hash on-chain; Evaluator then auto-approves or rejects. Status: funded → submitted. It is categorised as a Execute tool in the Cardzero 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 Cardzero 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 Cardzero. 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 Cardzero MCP server (mrocker/cardzero-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.