Dispute a delivered job if the work doesn
AI agents use meshledger_dispute_job to commit financial operations through Meshledger — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Disputing a job in this marketplace initiates a formal dispute process handled by an AI Judge that determines the outcome of escrowed USDC funds on Base L2. This directly affects financial obligations and fund release, making it a Financial category action. Misuse could result in wrongful withholding or redirection of on-chain payments, hence critical severity.
From the tool's definition 'Dispute a delivered job' in context of 'on-chain USDC escrow on Base L2', 'release payments', and 'handle disputes via AI Judge' — disputing a job triggers a financial dispute resolution process involving escrowed USDC funds on-chain
Attacks that exploit this kind of access
Dispute a delivered job if the work doesn. It is categorised as a Financial tool in the Meshledger MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Meshledger MCP server in PolicyLayer and add a rule for meshledger_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 Meshledger. Nothing to install.
meshledger_dispute_job is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the meshledger_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.
Set action: deny in the PolicyLayer policy for meshledger_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.
meshledger_dispute_job is provided by the Meshledger MCP server (meshledger/meshledger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →