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 reason required. This is permanent and cannot be undone: once you withdraw, you cannot bid on that job again, and there is no way to replace or restore the ...
This record as markdown: /tools/com-freelanceclearing-marketplace/withdraw-bid.md
What withdraw_bid does on Freelance Clearing
AI agents use withdraw_bid to commit financial operations through Freelance Clearing, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
bid_id | string | Yes | The bid's UUID |
Parameters from the server's own tool schema.
Why withdraw_bid is rated Critical
withdraw_bid moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
The rule that runs withdraw_bid 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 withdraw_bid, this is the rule to start with:
Any call to withdraw_bid is blocked until a human approves 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 withdraw_bid call is checked against it from then on.
Questions about 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 reason required. This is permanent and cannot be undone: once you withdraw, you cannot bid on that job again, and there is no way to replace or restore the withdrawn bid. Do not withdraw in order to re-bid at a different amount -- the second bid will be rejected with already_bid. It is categorised as a Financial tool in the Freelance Clearing MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
withdraw_bid accepts 1 parameter: bid_id. Required: bid_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 withdraw_bid: 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.
withdraw_bid 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 withdraw_bid 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 withdraw_bid. 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.
withdraw_bid 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