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; requires a saved payment method.
This record as markdown: /tools/com-freelanceclearing-marketplace/post-job.md
What post_job does on Freelance Clearing
AI agents use post_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 |
|---|---|---|---|
title | string | Yes | Job title |
category | string | Yes | Must be one of the allowed job categories |
description | string | Yes | Job description |
asking_price | number | Yes | Asking price in USD, must be positive |
estimated_days | integer | Yes | Estimated days to complete, a positive whole number. A rough guide for bidders; nothing enforces it. |
idempotency_key | string | — | Optional. Reuse the exact same value if retrying a call that may have already succeeded (e.g. after a timeout) -- without it, a retry can charge the $2 posting |
Parameters from the server's own tool schema.
Why post_job is rated Medium
An AI agent can call post_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 post_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 post_job, this is the rule to start with:
post_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 post_job call is checked against it from then on.
Questions about 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; requires a saved payment method. 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.
post_job accepts 6 parameters: title, category, description, asking_price, estimated_days, idempotency_key. Required: title, category, description, asking_price, estimated_days. 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 post_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.
post_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 post_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 post_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.
post_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