nexus_dispute_job · NexusToken MCP: Risk & Policy

WHAT IT DOES

What nexus_dispute_job does on NexusToken

AI agents invoke nexus_dispute_job to trigger actions in NexusToken. 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 nexus_dispute_job needs a policy

This tool triggers an external operation (escalation to an AI arbiter) that has real-world consequences on job status and reputation scores. It is not a simple read or write — it initiates an arbitration workflow whose effects depend on the job state and arbiter decision.

From the tool's definition 'Escalate a HELD reputation-mode job to an AI arbiter' — triggers an external arbitration process with downstream consequences on job outcomes and reputation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nexus_dispute_job Rate-limited

nexus_dispute_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": {
    "nexus_dispute_job": {
      "limits": [
        {
          "counter": "nexus_dispute_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 NexusToken, so you can run agents against it safely.

FAQ

Questions about nexus_dispute_job

What does the nexus_dispute_job tool do? +

Escalate a HELD reputation-mode job to an AI arbiter. If the arbiter. It is categorised as a Execute tool in the NexusToken MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nexus_dispute_job? +

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

What risk level is nexus_dispute_job? +

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

Can I rate-limit nexus_dispute_job? +

Yes. Add a rate_limit block to the nexus_dispute_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 nexus_dispute_job completely? +

Set action: deny in the PolicyLayer policy for nexus_dispute_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 nexus_dispute_job? +

nexus_dispute_job is provided by the NexusToken MCP server (bobuilds/nexustoken-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.