bounty_list
List bounties on aibtc.com/api/bounties. Filters: - status:
This record as markdown: /tools/io-github-aibtcdev-mcp-server/bounty-list.md
What bounty_list does on Aibtc
AI agents call bounty_list to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why bounty_list is rated Low
This tool retrieves or queries bounty data from an API endpoint without creating, modifying, or deleting any data. The sole parameter (status filter) is used for filtering results, not performing actions. This is a standard Read operation with minimal risk.
From the tool's definition Tool name "bounty_list" and description "List bounties" indicate a retrieval operation with no side effects. The presence of a "status" filter confirms this is a query/search function.
Attacks that exploit this kind of access
The rule that runs bounty_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bounty_list, this is the rule to start with:
bounty_list 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 Aibtc, apply this rule, and every bounty_list call is checked against it from then on.
Questions about bounty_list
List bounties on aibtc.com/api/bounties. Filters: - status:. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for bounty_list: 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 Aibtc. Nothing to install.
bounty_list 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 bounty_list 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 bounty_list. 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.
bounty_list is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue