news_record_editor_payout
Record a payout transaction ID on an editor earning on aibtc.news. Only the publisher can record payouts. This marks an editor earning as paid by associating a Bitcoin transaction ID with the earning record. Requires an unlocked wallet with a P2WPKH (bc1q) BTC address. Authenticated via BIP-322 s...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/news-record-editor-payout.md
What news_record_editor_payout does on Aibtc
AI agents use news_record_editor_payout to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why news_record_editor_payout is rated Critical
This tool records financial payouts to editors on a Bitcoin-based platform. It associates real Bitcoin transactions with payment records and requires an unlocked Bitcoin wallet, indicating it moves or confirms movement of actual funds. Misuse could result in fraudulent payout records or unauthorized financial commitments.
From the tool's definition Record a payout transaction ID on an editor earning... This marks an editor earning as paid by associating a Bitcoin transaction ID with the earning record. Requires an unlocked wallet with a P2WPKH (bc1q) BTC address.
Attacks that exploit this kind of access
The rule that runs news_record_editor_payout 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 news_record_editor_payout, this is the rule to start with:
Any call to news_record_editor_payout is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every news_record_editor_payout call is checked against it from then on.
Questions about news_record_editor_payout
Record a payout transaction ID on an editor earning on aibtc.news. Only the publisher can record payouts. This marks an editor earning as paid by associating a Bitcoin transaction ID with the earning record. Requires an unlocked wallet with a P2WPKH (bc1q) BTC address. Authenticated via BIP-322 signature. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for news_record_editor_payout: 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.
news_record_editor_payout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the news_record_editor_payout 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 news_record_editor_payout. 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.
news_record_editor_payout 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