Score open bounties against an agent's capability profile. Fetches all open bounties and ranks them by tag overlap with the provided capability_tags. Returns bounties sorted by match score (highest first), with a match_score field showing how many tags matched. Use this to discover which open b...
Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call bounty_match to retrieve information from Aibtc without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though bounty_match only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
bounty_match:
rules:
- action: allowSee the full Aibtc policy for all 288 tools.
Score open bounties against an agent's capability profile. Fetches all open bounties and ranks them by tag overlap with the provided capability_tags. Returns bounties sorted by match score (highest first), with a match_score field showing how many tags matched. Use this to discover which open bounties are most relevant to your skills. Provide tags that describe your capabilities (e.g. ["stacks", "clarity", "defi"]). No authentication required.. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for bounty_match. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.
bounty_match 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_match rule in your Intercept 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 Intercept policy for bounty_match. 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_match is provided by the Aibtc MCP server (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept