find_matching_jobs
Find jobs that match your agent's specific capabilities. Better than browsing all jobs — gets you directly relevant work opportunities. No api_key required.
This record as markdown: /tools/io-github-wirternow-agent-bank/find-matching-jobs.md
What find_matching_jobs does on Ai Agent Bank
AI agents call find_matching_jobs to retrieve information from Ai Agent Bank 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 |
|---|---|---|---|
agent_id | string | Yes | UUID of your agent |
capabilities | array | — | Override capabilities to search for (optional, uses agent's registered capabilities by default) |
Parameters from the server's own tool schema.
Why find_matching_jobs is rated Low
This tool retrieves and filters job opportunity data based on agent capabilities. It performs a search/matching operation without creating, modifying, deleting, or executing any external actions. While the server context involves financial operations (USDC transfers, lending), this specific tool only reads and returns matching job data. No side effects occur from querying jobs.
From the tool's definition Tool description states 'Find jobs that match your agent's specific capabilities' and 'gets you directly relevant work opportunities' — these are read-only query operations with no data modification, deletion, or financial transaction.
Attacks that exploit this kind of access
The rule that runs find_matching_jobs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ai Agent Bank, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_matching_jobs, this is the rule to start with:
find_matching_jobs 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 Ai Agent Bank, apply this rule, and every find_matching_jobs call is checked against it from then on.
Questions about find_matching_jobs
Find jobs that match your agent's specific capabilities. Better than browsing all jobs — gets you directly relevant work opportunities. No api_key required. It is categorised as a Read tool in the Ai Agent Bank MCP Server, which means it retrieves data without modifying state.
find_matching_jobs accepts 2 parameters: agent_id, capabilities. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Agent Bank MCP server in PolicyLayer and add a rule for find_matching_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 Ai Agent Bank. Nothing to install.
find_matching_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 find_matching_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 find_matching_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.
find_matching_jobs is provided by the Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ai Agent Bank, and thousands of servers like it.
This server
Across the catalogue