get_cash_flow
Get company cash flow statement data.
This record as markdown: /tools/zwldarren-akshare-one-mcp/get-cash-flow.md
What get_cash_flow does on AKShare One MCP Server
AI agents call get_cash_flow to retrieve information from AKShare One MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
source | string | — | Data source |
symbol | string | — | Stock symbol/ticker (e.g. '000001') |
recent_n | object | — | Number of most recent records to return |
Parameters from the server's own tool schema.
Why get_cash_flow is rated Low
This tool retrieves historical financial data (cash flow statements) from the AKShare stock market database. It queries and returns data with no side effects, modifications, or irreversible changes. This is a straightforward read operation consistent with the sibling tools on this server (get_balance_sheet, get_income_statement, etc.), all of which are data retrieval functions.
From the tool's definition Tool name 'get_cash_flow' and description 'Get company cash flow statement data' indicate retrieval of financial statement information. No modification, deletion, or execution of external operations is performed.
Attacks that exploit this kind of access
The rule that runs get_cash_flow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AKShare One MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cash_flow, this is the rule to start with:
get_cash_flow 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 AKShare One MCP Server, apply this rule, and every get_cash_flow call is checked against it from then on.
Questions about get_cash_flow
Get company cash flow statement data. It is categorised as a Read tool in the AKShare One MCP Server MCP Server, which means it retrieves data without modifying state.
get_cash_flow accepts 3 parameters: source, symbol, recent_n. The full parameter table on this page comes from the server's own tool schema.
Register the AKShare One MCP Server MCP server in PolicyLayer and add a rule for get_cash_flow: 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 AKShare One MCP Server. Nothing to install.
get_cash_flow 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 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. 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 is provided by the AKShare One MCP Server MCP server (zwldarren/akshare-one-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AKShare One MCP Server, and thousands of servers like it.
This server
Across the catalogue