Get up to 10 years of quarterly cash position history from SEC XBRL filings
AI agents call get_cash_history to retrieve information from Signal8 MCP Server 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 positions) from SEC filings. It is a read-only query operation with no side effects—it does not create, modify, delete, execute code, or move money. The data comes from public SEC filings (XBRL format), making it informational only.
From the tool's definition Tool name 'get_cash_history' and description 'Get up to 10 years of quarterly cash position history from SEC XBRL filings' indicate pure data retrieval from public SEC filings with no modification, deletion, execution, or financial transaction capabilities.
Attacks that exploit this kind of access
Get up to 10 years of quarterly cash position history from SEC XBRL filings. It is categorised as a Read tool in the Signal8 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Signal8 MCP Server MCP server in PolicyLayer and add a rule for get_cash_history: 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 Signal8 MCP Server. Nothing to install.
get_cash_history 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_history 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_history. 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_history is provided by the Signal8 MCP Server MCP server (signal8ai/signal8-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 →