get_history_funds_flow_tool
AI agents call get_history_funds_flow_tool to retrieve information from FNewsCrawler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve historical financial data (funds flow), which is a read operation with no side effects. The 'get_' prefix and context of sibling read-only query tools indicate it queries existing data without modification.
From the tool's definition Tool name 'get_history_funds_flow_tool' indicates retrieval of historical fund flow data. Sibling tools on this server follow a consistent 'get_*' pattern (get_ak_news_cctv, get_ak_stock_news_em, get_eastmoney_market_history_funds_flow) all performing data…
Attacks that exploit this kind of access
get_history_funds_flow_tool. It is categorised as a Read tool in the FNewsCrawler MCP Server, which means it retrieves data without modifying state.
Register the FNewsCrawler MCP server in PolicyLayer and add a rule for get_history_funds_flow_tool: 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 FNewsCrawler. Nothing to install.
get_history_funds_flow_tool 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_history_funds_flow_tool 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_history_funds_flow_tool. 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_history_funds_flow_tool is provided by the FNewsCrawler MCP server (noimank/fnewscrawler). 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 →