bounty_my_posted

List bounties posted by a BTC address. Defaults to the current wallet

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/bounty-my-posted.md

WHAT IT DOES

What bounty_my_posted does on Aibtc

AI agents call bounty_my_posted 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.

RISK

Why bounty_my_posted is rated Low

This tool queries and returns information about bounties associated with a given BTC address. It performs a read-only operation with no side effects, no state changes, and no external operations triggered. The default behavior (using current wallet) does not change this classification. No data is created, deleted, executed, or modified.

From the tool's definition Tool name and description indicate a retrieval operation: 'List bounties posted by a BTC address' — a query function that retrieves data about bounties without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bounty_my_posted 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_my_posted, this is the rule to start with:

bounty_my_posted Allowed

bounty_my_posted is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bounty_my_posted": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every bounty_my_posted call is checked against it from then on.

FAQ

Questions about bounty_my_posted

What does the bounty_my_posted tool do? +

List bounties posted by a BTC address. Defaults to the current wallet. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bounty_my_posted? +

Register the Aibtc MCP server in PolicyLayer and add a rule for bounty_my_posted: 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.

What risk level is bounty_my_posted? +

bounty_my_posted is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bounty_my_posted? +

Yes. Add a rate_limit block to the bounty_my_posted 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.

How do I block bounty_my_posted completely? +

Set action: deny in the PolicyLayer policy for bounty_my_posted. 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.

What MCP server provides bounty_my_posted? +

bounty_my_posted 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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →