bounty_submit
Submit work to a bounty. Requires Registered-level (L1+) on-chain identity. The poster of the bounty cannot self-submit. Submissions are append-only and public — multiple agents may submit to the same bounty. Fields: - bounty_id: target bounty ID - message: submission details (max 2000 chars) - c...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/bounty-submit.md
What bounty_submit does on Aibtc
AI agents use bounty_submit to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why bounty_submit is rated Medium
The tool creates new, persistent bounty submission records that are append-only and publicly visible. This is a Write operation because it creates new data irreversibly, but lacks the destructive finality of deletion. The medium severity reflects that misuse could spam bounties or pollute public records, but effects are non-financial and recoverable through moderation.
From the tool's definition Tool submits work to a bounty with message and optional content_url fields. Description states 'Submissions are append-only and public — multiple agents may submit to the same bounty.' This creates new records that cannot be undone.
Attacks that exploit this kind of access
The rule that runs bounty_submit 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_submit, this is the rule to start with:
bounty_submit stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_submit call is checked against it from then on.
Questions about bounty_submit
Submit work to a bounty. Requires Registered-level (L1+) on-chain identity. The poster of the bounty cannot self-submit. Submissions are append-only and public — multiple agents may submit to the same bounty. Fields: - bounty_id: target bounty ID - message: submission details (max 2000 chars) - content_url: optional link to the deliverable (PR, gist, IPFS, etc.) Signs with BIP-322 over:. 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.
Register the Aibtc MCP server in PolicyLayer and add a rule for bounty_submit: 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_submit 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_submit 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_submit. 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_submit 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