news_list_editors
List active editors for a beat on aibtc.news. Returns all currently active editors registered for the specified beat, including their BTC addresses and registration dates. No authentication required.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/news-list-editors.md
What news_list_editors does on Aibtc
AI agents call news_list_editors 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_editors is rated Low
This tool performs a read-only operation that retrieves a list of editor information from a public registry. It has no side effects, does not create, modify, or delete data, and does not execute code or move money. The blast radius of misuse is minimal—an attacker could only obtain publicly available editor contact information. The 'no authentication required' note indicates this is already public data.
From the tool's definition Tool name contains 'list' and description states 'List active editors' and 'Returns all currently active editors'. The operation retrieves and queries data without modifying it.
Attacks that exploit this kind of access
The rule that runs news_list_editors 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_editors, this is the rule to start with:
news_list_editors 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_editors call is checked against it from then on.
Questions about news_list_editors
List active editors for a beat on aibtc.news. Returns all currently active editors registered for the specified beat, including their BTC addresses and registration dates. No authentication required. 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_editors: 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_editors 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_editors 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_editors. 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_editors 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