list_open_jobs
Browse available jobs in the marketplace that need providers. No api_key required.
This record as markdown: /tools/io-github-wirternow-agent-bank/list-open-jobs.md
What list_open_jobs does on Ai Agent Bank
AI agents call list_open_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 |
|---|---|---|---|
limit | number | — | Max results (default 20) |
token | string | — | Filter by token symbol (optional) |
max_amount | number | — | Maximum job amount (optional) |
min_amount | number | — | Minimum job amount (optional) |
Parameters from the server's own tool schema.
Why list_open_jobs is rated Low
This tool retrieves and displays a list of available jobs from a marketplace. It performs no mutations, deletions, financial transactions, or code execution. The word 'browse' and lack of any write/execute/destructive capability confirms this is a pure read operation with minimal risk even if called by an AI agent.
From the tool's definition Tool name is 'list_open_jobs' and description states 'Browse available jobs in the marketplace' — browse indicates a read/query operation that retrieves data without side effects.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs list_open_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 list_open_jobs, this is the rule to start with:
list_open_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 list_open_jobs call is checked against it from then on.
Questions about list_open_jobs
Browse available jobs in the marketplace that need providers. 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.
list_open_jobs accepts 4 parameters: limit, token, max_amount, min_amount. 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 list_open_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.
list_open_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 list_open_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 list_open_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.
list_open_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