// SCAN REPORT

Freelance Clearing

20 tools. 8 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 26 Aug 2026

8 can modify or destroy data

12 read-only

20 tools total

Community server · catalogue entry checked 26/08/2026 · full schemas captured for 19 of 20 tools

How to control Freelance Clearing ↓

TOOL MAP

What Freelance Clearing exposes to your agents

Read (12) Write / Execute (6) Destructive / Financial (2)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Freelance Clearing costs in tokens

5,375 tokens of tool definitions, loaded on every request

2.7% of a 200k context window

402 heaviest tool: browse_users

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Freelance Clearing tools

Financial · Critical withdraw_bid Withdraw your own bid on a job, as the bidder who placed it. Only possible while the job is still open and your bid hasn't been accepted. No Destructive · Critical 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 i Write · Medium complete_job Mark a job as complete, as that job's poster. Moves the job from in_progress to completed. Only the poster can do this -- not even the accep Write · Medium post_job Post a new job listing, as the authenticated user. Equivalent to the website's "Post a Job" form. Charges a $2 posting fee immediately; requ

8 of Freelance Clearing's 20 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Freelance Clearing

PolicyLayer is an MCP gateway — it sits between your AI agents and Freelance Clearing, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "withdraw_bid": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations

{
  "cancel_job": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "complete_job": {
    "limits": [
      {
        "counter": "complete_job_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "accept_bid": {
    "limits": [
      {
        "counter": "accept_bid_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Freelance Clearing — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FREELANCE CLEARING →

Instant setup, no code required.

FULL CATALOGUE

All 20 Freelance Clearing tools

FINANCIAL 1 tools

Financial withdraw_bid Withdraw your own bid on a job, as the bidder who placed it. Only possible while the job is still open and you

DESTRUCTIVE 1 tools

Destructive 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 th

WRITE 6 tools

Write complete_job Mark a job as complete, as that job's poster. Moves the job from in_progress to completed. Only the poster can Write post_job Post a new job listing, as the authenticated user. Equivalent to the website's "Post a Job" form. Charges a $2 Write request_close Ask the poster to close an in-progress job, as the freelancer working on it. Use this after delivering, when t Write send_message Send a message on a job to a specific other participant. If you're the poster, the recipient must be someone w Write submit_bid Submit a bid on an open job, as the authenticated user. You can't bid on your own job. You get one bid per job Write submit_rating Rate your counterparty on a job that's completed or cancelled. Only the poster and the accepted bidder can rat

READ 12 tools

Read accept_bid Accept a specific bid on a job, as that job's poster. Moves the job to in_progress. Only the job's poster can Read browse_jobs List jobs on Freelance Clearing (equivalent to the Browse page's Jobs tab). Defaults to OPEN jobs only, which Read browse_users List the people on Freelance Clearing (equivalent to the Browse page's Users tab), with the same facts a perso Read get_bids List the bids on a job. While the job is still open, only the job's poster can see the list (so bidders can't Read get_document Fetch one of this site's published documents in full, as markdown: the Terms of Service, the Privacy Policy, o Read get_job Fetch full detail for a single job by id, regardless of its status (open, in progress, completed, or cancelled Read get_me Get your own identity and capabilities: user id, username, join date, rating, and whether you can currently po Read get_messages Read the messages for a job. The job's poster sees every conversation on that job (with every bidder they've m Read get_my_jobs List jobs you've posted and/or bid on, with pagination. Posted jobs carry the bid count and accepted bidder (o Read get_ratings Read individual ratings, including the written review text -- not just the average that job results inline. Pa Read get_user Fetch a user's public profile by username: description, join date, rating average and count, completed jobs, c Read get_user_jobs List what one user has posted and bid on -- the same lists the website's profile page shows to anyone. Same sh

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Freelance Clearing

Can an AI agent move money through the Freelance Clearing MCP server? +

Yes. The Freelance Clearing server exposes 1 financial tools including withdraw_bid. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Freelance Clearing MCP server? +

Yes. The Freelance Clearing server exposes 1 destructive tools including cancel_job. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Freelance Clearing? +

The Freelance Clearing server has 6 write tools including complete_job, post_job, request_close. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Freelance Clearing.

How many tools does the Freelance Clearing MCP server expose? +

20 tools across 4 categories: Destructive, Financial, Read, Write. 12 are read-only. 8 can modify, create, or delete data.

How do I enforce a policy on Freelance Clearing? +

Register the Freelance Clearing MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Freelance Clearing tool call.

Deterministic rules across all 20 Freelance Clearing tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FREELANCE CLEARING →

Instant setup, no code required.

20 Freelance Clearing tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Freelance Clearing's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →