AI agents call get_news_article to retrieve information from Ib Async without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves news article data, which is a Read operation. The severity is low because news retrieval has no impact on account state, positions, or financial obligations.
From the tool's definition Tool name 'get_news_article' and description 'Get a news article' indicate a retrieval operation with no side effects. This is a read-only query against market news data.
Attacks that exploit this kind of access
Get a news article. It is categorised as a Read tool in the Ib Async MCP Server, which means it retrieves data without modifying state.
Register the Ib Async MCP server in PolicyLayer and add a rule for get_news_article: 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 Ib Async. Nothing to install.
get_news_article 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 get_news_article 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 get_news_article. 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.
get_news_article is provided by the Ib Async MCP server (nadavgb-atom/ib-async-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →