bounty_submissions
Paginated list of submissions for a single bounty. Submissions are public (the inbox is public, so are bounty submissions). No authentication required.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/bounty-submissions.md
What bounty_submissions does on Aibtc
AI agents call bounty_submissions 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_submissions is rated Low
This tool queries and retrieves existing public bounty submission data. It performs no modifications, deletions, or external operations. The paginated list pattern is characteristic of read-only data retrieval. No financial, destructive, or execution capabilities are present.
From the tool's definition Tool name 'bounty_submissions' and description state it is a 'Paginated list of submissions for a single bounty.' The description explicitly notes submissions are 'public' and 'no authentication required,' indicating this retrieves public data without side…
Attacks that exploit this kind of access
The rule that runs bounty_submissions 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_submissions, this is the rule to start with:
bounty_submissions 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_submissions call is checked against it from then on.
Questions about bounty_submissions
Paginated list of submissions for a single bounty. Submissions are public (the inbox is public, so are bounty submissions). No authentication required. 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_submissions: 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_submissions 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_submissions 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_submissions. 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_submissions 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