Search Upwork jobs. Optimized for n8n/automation niche. Returns job list with budget, client info, proposal count.
AI agents call search_jobs to retrieve information from Upwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_jobs performs a query operation that retrieves and lists job postings along with metadata (budget, client info, proposal count). No data is created, modified, deleted, or executed. The tool has no side effects beyond returning information.
From the tool's definition Tool description states it "Search[es] Upwork jobs" and "Returns job list with budget, client info, proposal count." These are retrieval operations with no modification or execution of external actions.
Documented attack patterns abuse exactly the kind of access search_jobs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Upwork, and nothing reaches the server without passing your rules. This is the rule we recommend for search_jobs:
{
"version": "1",
"default": "deny",
"tools": {
"search_jobs": {}
}
} search_jobs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search Upwork jobs. Optimized for n8n/automation niche. Returns job list with budget, client info, proposal count. It is categorised as a Read tool in the Upwork MCP Server, which means it retrieves data without modifying state.
Register the Upwork MCP server in PolicyLayer and add a rule for search_jobs: 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 Upwork. Nothing to install.
search_jobs 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 search_jobs 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 search_jobs. 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.
search_jobs is provided by the Upwork MCP server (zcrossoverz/upwork-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Upwork, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Upwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.