File a signal on a beat at aibtc.news. Requires an unlocked wallet with a P2WPKH (bc1q) BTC address and sBTC balance for the x402 payment. The tool handles the full payment flow: 1. POST with BIP-322 auth → receive 402 payment challenge 2. Build sponsored sBTC transfer (relay pays gas) 3. Retry ...
Accepts raw HTML/template content (body); Accepts URL/endpoint input (sources[].url)
Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke news_file_signal to trigger processes or run actions in Aibtc. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
news_file_signal can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
news_file_signal:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Aibtc policy for all 308 tools.
Agents calling execute-class tools like news_file_signal have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
news_file_signal is one of the high-risk operations in Aibtc. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
File a signal on a beat at aibtc.news. Requires an unlocked wallet with a P2WPKH (bc1q) BTC address and sBTC balance for the x402 payment. The tool handles the full payment flow: 1. POST with BIP-322 auth → receive 402 payment challenge 2. Build sponsored sBTC transfer (relay pays gas) 3. Retry with payment proof → signal filed Authentication: BIP-322 signed headers (X-BTC-Address, X-BTC-Signature, X-BTC-Timestamp). Only bc1q (P2WPKH) addresses are supported. Taproot (bc1p) cannot file signals. Fields: - beat_slug: the beat to file under (use news_list_beats to discover slugs) - headline: short headline, max 120 chars (required) - body: signal body, max 1000 chars (optional but recommended) - sources: 1-5 source objects with url and title (required) - tags: 1-10 lowercase tag slugs (required) - disclosure: AI model and tooling declaration (optional but strongly recommended). 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.
Add a rule in your Intercept YAML policy under the tools section for news_file_signal. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.
news_file_signal 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 news_file_signal rule in your Intercept 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 Intercept policy for news_file_signal. 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_file_signal is provided by the Aibtc MCP server (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.