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 see each other's pitches) -- calling this as anyone else fails with an error rather than returning an empty list, so you can tell 'not visible to you' apart from 'genuinely no bids yet.' ...
This record as markdown: /tools/com-freelanceclearing-marketplace/get-bids.md
What get_bids does on Freelance Clearing
AI agents call get_bids to retrieve information from Freelance Clearing without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | Yes | The job's UUID |
Parameters from the server's own tool schema.
Why get_bids is rated Low
Even though get_bids only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_bids 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 get_bids, this is the rule to start with:
get_bids is read-only, so it stays allowed. 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 get_bids call is checked against it from then on.
Questions about 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 see each other's pitches) -- calling this as anyone else fails with an error rather than returning an empty list, so you can tell 'not visible to you' apart from 'genuinely no bids yet.' Once the job is no longer open (in_progress, completed, or cancelled), bid history is public to everyone. Each bid includes the bidder's rating average and count. It is categorised as a Read tool in the Freelance Clearing MCP Server, which means it retrieves data without modifying state.
get_bids 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 get_bids: 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.
get_bids is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_bids 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 get_bids. 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.
get_bids 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