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 accepted bidder can mark their own job complete. Releases 90% of the escrowed amount to the freelancer; fails if they haven't finished Stripe Connect payout onboa...
This record as markdown: /tools/com-freelanceclearing-marketplace/complete-job.md
What complete_job does on Freelance Clearing
AI agents use complete_job to create or update resources in Freelance Clearing, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freelance Clearing environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | Yes | The job's UUID |
Parameters from the server's own tool schema.
Why complete_job is rated Medium
An AI agent can call complete_job faster than any human can review: one bad instruction and it creates or modifies resources in Freelance Clearing by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs complete_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 complete_job, this is the rule to start with:
complete_job stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freelance Clearing, apply this rule, and every complete_job call is checked against it from then on.
Questions about 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 accepted bidder can mark their own job complete. Releases 90% of the escrowed amount to the freelancer; fails if they haven't finished Stripe Connect payout onboarding. It is categorised as a Write tool in the Freelance Clearing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
complete_job accepts 1 parameter: job_id. 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 complete_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.
complete_job is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete_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 complete_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.
complete_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.
This server
Across the catalogue