Get SEC filings for a stock (10-K, 10-Q, 8-K, etc.).
AI agents call get_sec_filings to retrieve information from yfinance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
SEC filings are public documents; retrieving them has no side effects and poses minimal risk. This is a straightforward data query operation analogous to other Read tools on the server (get_historical_data, get_dividends, get_financials, get_earnings). An AI agent cannot cause harm by retrieving SEC filing information.
From the tool's definition Tool description states 'Get SEC filings' — a retrieval operation that queries publicly available SEC filing data. No modification, deletion, execution of code, or financial transaction occurs. The tool name and description indicate data retrieval only.
Attacks that exploit this kind of access
Get SEC filings for a stock (10-K, 10-Q, 8-K, etc.). It is categorised as a Read tool in the yfinance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the yfinance MCP Server MCP server in PolicyLayer and add a rule for get_sec_filings: 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 yfinance MCP Server. Nothing to install.
get_sec_filings 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_sec_filings 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_sec_filings. 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_sec_filings is provided by the yfinance MCP Server MCP server (torosent/yfinance-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 →