Fetch cash flow statement data for a company.
AI agents call get_cash_flow_statement to retrieve information from Yfnhanced without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical financial data (cash flow statements) from Yahoo Finance. It is analogous to the sibling tools like 'get_balance_sheet', 'get_income_statement', and 'get_historical_prices', which are all Read operations that query data without side effects. No money moves, no data is modified or deleted, and no external operations are triggered.
From the tool's definition Tool name 'get_cash_flow_statement' and description 'Fetch cash flow statement data for a company' indicate a retrieval operation with no modification, deletion, or financial transaction capability. The verb 'Fetch' confirms read-only semantics.
Documented attack patterns abuse exactly the kind of access get_cash_flow_statement gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yfnhanced, and nothing reaches the server without passing your rules. This is the rule we recommend for get_cash_flow_statement:
{
"version": "1",
"default": "deny",
"tools": {
"get_cash_flow_statement": {}
}
}get_cash_flow_statement is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch cash flow statement data for a company. It is categorised as a Read tool in the Yfnhanced MCP Server, which means it retrieves data without modifying state.
Register the Yfnhanced MCP server in PolicyLayer and add a rule for get_cash_flow_statement: 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 Yfnhanced. Nothing to install.
get_cash_flow_statement 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_cash_flow_statement 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_cash_flow_statement. 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_cash_flow_statement is provided by the Yfnhanced MCP server (kanishka-namdeo/yfnhanced-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Yfnhanced, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Yfnhanced tools catalogued and risk-classified — across an index of 43,000+ MCP servers.