Create a new bounty on bounty.drx4.xyz. Posts a new bounty to the sBTC bounty board. Requires an unlocked wallet with BTC keys and AIBTC level >= 1. The request is authenticated via BIP-322 signing. Fields: - title: short descriptive title for the bounty - description: full details of the task,...
Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use bounty_create to create or modify resources in Aibtc. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call bounty_create repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Aibtc.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
bounty_create:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Aibtc policy for all 308 tools.
Agents calling write-class tools like bounty_create have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Create a new bounty on bounty.drx4.xyz. Posts a new bounty to the sBTC bounty board. Requires an unlocked wallet with BTC keys and AIBTC level >= 1. The request is authenticated via BIP-322 signing. Fields: - title: short descriptive title for the bounty - description: full details of the task, deliverables, and acceptance criteria - amount_sats: reward amount in satoshis - tags: comma-separated tags (e.g. "stacks,defi,clarity") - deadline: optional ISO 8601 deadline (e.g. "2026-04-15T00:00:00Z"). It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for bounty_create. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.
bounty_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bounty_create 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_create. 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_create 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.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.