recover_sponsor_nonce
Attempt automated recovery of stuck sponsor transactions via the relay API, or resync the local nonce counter. Run check_relay_health first to identify stuck txids and missing nonces, then use this tool to trigger recovery without needing to contact the AIBTC team manually. Recovery modes: - rbf:...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/recover-sponsor-nonce.md
What recover_sponsor_nonce does on Aibtc
AI agents invoke recover_sponsor_nonce to trigger actions in Aibtc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why recover_sponsor_nonce is rated High
This tool triggers external blockchain operations (rebroadcasting transactions with higher fees, submitting placeholder transactions) via a relay API. These are real on-chain actions with irreversible effects and potential financial implications (higher fees paid), but the primary classification is Execute as it triggers external operations.
From the tool's definition Attempt automated recovery of stuck sponsor transactions via the relay API... trigger recovery... rbf: Replace-by-fee — rebroadcasts stuck transactions with a higher fee... fill-gaps: Nonce gap-fill — submits placeholder transactions to fill any missing nonces
Attacks that exploit this kind of access
The rule that runs recover_sponsor_nonce 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 recover_sponsor_nonce, this is the rule to start with:
recover_sponsor_nonce stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 recover_sponsor_nonce call is checked against it from then on.
Questions about recover_sponsor_nonce
Attempt automated recovery of stuck sponsor transactions via the relay API, or resync the local nonce counter. Run check_relay_health first to identify stuck txids and missing nonces, then use this tool to trigger recovery without needing to contact the AIBTC team manually. Recovery modes: - rbf: Replace-by-fee — rebroadcasts stuck transactions with a higher fee so miners prioritize them. Provide specific txids or omit to bump all stuck transactions. - fill-gaps: Nonce gap-fill — submits placeholder transactions to fill any missing nonces that are blocking the queue. Provide specific nonces or omit to fill all gaps. - both: Attempt both RBF and gap-fill in sequence (default). - resync-local-nonce: Force-reset the MCP server. It is categorised as a Execute tool in the Aibtc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aibtc MCP server in PolicyLayer and add a rule for recover_sponsor_nonce: 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.
recover_sponsor_nonce is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the recover_sponsor_nonce 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 recover_sponsor_nonce. 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.
recover_sponsor_nonce 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.
Across the catalogue