New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browse_users

List the people on Freelance Clearing (equivalent to the Browse page's Users tab), with the same facts a person sees: username, description, join date, rating average and count, completed jobs, jobs posted, jobs bid on, and totals earned and paid. Only verified accounts appear. Sort and filter as...

SERVERFreelance Clearing SOURCEhttps://freelanceclearing.com/api/mcp
Low RISK CLASS
Category Read
Parameters 50 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-freelanceclearing-marketplace/browse-users.md

What browse_users does on Freelance Clearing

AI agents call browse_users 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.

ParameterTypeRequiredDescription
role string Default everyone. 'posters' is anyone who has posted at least one job, 'freelancers' anyone who has placed at least one bid. Somebody who has done both matches
sort string Default highest_rated, the same default the website's Users tab opens on. Users with no ratings sort last under highest_rated.
limit integer Default 25, maximum 100.
offset integer Default 0. Use with the pagination block in the response.
rating string Default any. '4up' means an average of 4 or better; 'not_rated' means no ratings at all.

Parameters from the server's own tool schema.

Why browse_users is rated Low

Even though browse_users 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.

Questions about browse_users

What does the browse_users tool do? +

List the people on Freelance Clearing (equivalent to the Browse page's Users tab), with the same facts a person sees: username, description, join date, rating average and count, completed jobs, jobs posted, jobs bid on, and totals earned and paid. Only verified accounts appear. Sort and filter as you like -- the platform publishes the figures and you decide what matters; nothing here ranks people for you. Use it to find someone to hire when you have no job to start from, which is otherwise impossible: without it a counterparty can only be reached by first finding a job they posted or bid on. It is categorised as a Read tool in the Freelance Clearing MCP Server, which means it retrieves data without modifying state.

What parameters does browse_users accept? +

browse_users accepts 5 parameters: role, sort, limit, offset, rating. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browse_users? +

Register the Freelance Clearing MCP server in PolicyLayer and add a rule for browse_users: 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.

What risk level is browse_users? +

browse_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browse_users? +

Yes. Add a rate_limit block to the browse_users 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.

How do I block browse_users completely? +

Set action: deny in the PolicyLayer policy for browse_users. 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.

What MCP server provides browse_users? +

browse_users 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Freelance Clearing's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.