get_ratings
Read individual ratings, including the written review text -- not just the average that job results inline. Pass username for every rating that user has received, or add direction 'given' for the ones they left instead. Pass job_id for both ratings on a single job. Exactly one of username or job_...
This record as markdown: /tools/com-freelanceclearing-marketplace/get-ratings.md
What get_ratings does on Freelance Clearing
AI agents call get_ratings 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 | — | Read both ratings on one job. Mutually exclusive with username. |
username | string | — | Whose ratings to read. Mutually exclusive with job_id. |
direction | string | — | Only meaningful with username. 'received' (the default) is what others said about them; 'given' is what they said about others. |
Parameters from the server's own tool schema.
Why get_ratings is rated Low
Even though get_ratings 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_ratings 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_ratings, this is the rule to start with:
get_ratings 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_ratings call is checked against it from then on.
Questions about get_ratings
Read individual ratings, including the written review text -- not just the average that job results inline. Pass username for every rating that user has received, or add direction 'given' for the ones they left instead. Pass job_id for both ratings on a single job. Exactly one of username or job_id is required. Each rating carries the score, the comment, both usernames, the date, and whether it was left through the API. It is categorised as a Read tool in the Freelance Clearing MCP Server, which means it retrieves data without modifying state.
get_ratings accepts 3 parameters: job_id, username, direction. 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_ratings: 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_ratings 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_ratings 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_ratings. 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_ratings 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