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

Agent View of the PolicyLayer registry record for `cancel_job`. HTML page: https://policylayer.com/tools/com-freelanceclearing-marketplace/cancel-job

## Facts

- Tool: `cancel_job`
- Server: Freelance Clearing (`https://freelanceclearing.com/api/mcp`) — https://policylayer.com/tools/com-freelanceclearing-marketplace.md
- Homepage: https://github.com/https://freelanceclearing.com/api/mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `job_id` | string | yes | The job's UUID |
| `reason` | string | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "cancel_job",
    "arguments": {
      "job_id": "<job_id>"
    }
  }
}
```

## 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 signals: Bulk/mass operation — affects multiple targets

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Freelance Clearing:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_job"
  ]
}
```

## Other tools on Freelance Clearing (19)

- `withdraw_bid` — Financial — https://policylayer.com/tools/com-freelanceclearing-marketplace/withdraw-bid.md
- `accept_bid` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/accept-bid.md
- `browse_jobs` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/browse-jobs.md
- `browse_users` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/browse-users.md
- `get_bids` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-bids.md
- `get_document` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-document.md
- `get_job` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-job.md
- `get_me` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-me.md
- `get_messages` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-messages.md
- `get_my_jobs` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-my-jobs.md
- `get_ratings` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-ratings.md
- `get_user` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-user.md
- `get_user_jobs` — Read — https://policylayer.com/tools/com-freelanceclearing-marketplace/get-user-jobs.md
- `complete_job` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/complete-job.md
- `post_job` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/post-job.md
- `request_close` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/request-close.md
- `send_message` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/send-message.md
- `submit_bid` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/submit-bid.md
- `submit_rating` — Write — https://policylayer.com/tools/com-freelanceclearing-marketplace/submit-rating.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-freelanceclearing-marketplace · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-freelanceclearing-marketplace