cancel_job
Cancel a job, either while it's still open (as the poster only) or while it's in progress (as the poster or the accepted bidder). A reason is required whenever the job is in progress, or when it's open with one or more existing bids -- otherwise it's optional. If the job is open with multiple bid...
This record as markdown: /tools/com-freelanceclearing-marketplace/cancel-job.md
What cancel_job does on Freelance Clearing
AI agents call cancel_job to permanently remove resources in Freelance Clearing, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | Yes | The job's UUID |
reason | string | — | Reason for canceling, shown to the other party/parties. Required unless the job is open with no bids. |
Parameters from the server's own tool schema.
Why cancel_job is rated Critical
An AI agent that decides to call cancel_job doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Freelance Clearing is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cancel_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freelance Clearing, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_job, this is the rule to start with:
cancel_job is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Freelance Clearing, apply this rule, and every cancel_job call is checked against it from then on.
Questions about cancel_job
Cancel a job, either while it's still open (as the poster only) or while it's in progress (as the poster or the accepted bidder). A reason is required whenever the job is in progress, or when it's open with one or more existing bids -- otherwise it's optional. If the job is open with multiple bidders, every one of them is notified individually. Cancelling in progress refunds 95% of escrow to the poster (5% retained); cancelling while open is free, but a $2 posting fee already paid is not refunded. It is categorised as a Destructive tool in the Freelance Clearing MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cancel_job accepts 2 parameters: job_id, reason. Required: job_id. The full parameter table on this page comes from the server's own tool schema.
Register the Freelance Clearing MCP server in PolicyLayer and add a rule for cancel_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 Freelance Clearing. Nothing to install.
cancel_job is a Destructive 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 cancel_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 cancel_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.
cancel_job is provided by the Freelance Clearing MCP server (https://freelanceclearing.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freelance Clearing, and thousands of servers like it.
Across the catalogue