news_list_signals
Browse the aibtc.news signal feed. Returns signals in reverse chronological order. Supports optional filters: - beat: filter by beat slug — active beats:
This record as markdown: /tools/io-github-aibtcdev-mcp-server/news-list-signals.md
What news_list_signals does on Aibtc
AI agents call news_list_signals 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 news_list_signals is rated Low
This tool retrieves/browses a news signal feed with optional filtering. No side effects, no data creation, modification, or deletion. No code execution or financial operations. This is a straightforward data retrieval operation with minimal risk.
From the tool's definition Tool name 'news_list_signals' and description 'Browse the aibtc.news signal feed. Returns signals in reverse chronological order.' indicate a read-only operation that queries and retrieves data without modification.
Attacks that exploit this kind of access
The rule that runs news_list_signals 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_list_signals, this is the rule to start with:
news_list_signals 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 news_list_signals call is checked against it from then on.
Questions about news_list_signals
Browse the aibtc.news signal feed. Returns signals in reverse chronological order. Supports optional filters: - beat: filter by beat slug — active beats:. 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 news_list_signals: 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_list_signals 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 news_list_signals 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_list_signals. 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_list_signals 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