Get pipeline-computed financial ratios from ratio.parquet. Served categories: profitability (margins, ROE, ROA, ROIC), liquidity (current ratio, quick ratio), leverage (D/E, interest coverage, net debt/EBITDA), efficiency (asset turnover, inventory days), per_share (EPS, BVPS, FCF/share), owner_e...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Valuein — SEC EDGAR Fundamentals & Smart-Money Data server.
Free to start. No card required.
AI agents call get_financial_ratios to retrieve information from Valuein — SEC EDGAR Fundamentals & Smart-Money Data without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_financial_ratios only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_financial_ratios": {}
}
}See the full Valuein — SEC EDGAR Fundamentals & Smart-Money Data policy for all 68 tools.
These attack patterns abuse exactly the kind of access get_financial_ratios gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get pipeline-computed financial ratios from ratio.parquet. Served categories: profitability (margins, ROE, ROA, ROIC), liquidity (current ratio, quick ratio), leverage (D/E, interest coverage, net debt/EBITDA), efficiency (asset turnover, inventory days), per_share (EPS, BVPS, FCF/share), owner_earnings (Buffett FCF, owner yield), and the pipeline-emitted forensic, growth, and rank (cross-sectional *_sector_pctile) categories. NOT every category exists for every ticker — the exact set is data-driven; omit categories to get whatever this ticker has, or read the available_categories list returned in the CATEGORY_NOT_AVAILABLE envelope. valuation (EV/EBITDA, P/E, P/FCF) is DECLARED BUT NOT YET POPULATED for any ticker (price feed pending) — requesting it returns a CATEGORY_NOT_AVAILABLE envelope, never data. Includes TTM (trailing twelve months) rows alongside annual periods. Each row carries is_calendar_aligned (boolean) — TRUE when period_end is actually on the entity's fiscal year boundary (±7 days), FALSE when the pipeline emitted a calendar-quarter row tagged fiscal_period='FY' for a non-December fiscal-year filer. Filter to is_calendar_aligned=TRUE if you're joining ratios with fact-table fundamentals on (entity, fiscal_year). Ratios are pipeline-derived — they're recomputed on each pipeline run with ON CONFLICT DO UPDATE. For historical cuts use as_of_date (the canonical cross-tool name; alias period_end_before). PIT semantics are data-driven: when the ratio data carries an SEC accepted_at timestamp, as_of_date filters point-in-time by accepted_at (zero look-ahead, latest-knowable per period) and _meta.pit_safe=true; when it does not (today's data), the cut is by ratio.period_end and _meta.pit_safe=false. For guaranteed accepted_at PIT regardless, use get_company_fundamentals (which carries fact.accepted_at). Use this *instead of* get_valuation_metrics when you only need ratios (no DCF wiring); use get_valuation_metrics when you also need DCF/DDM. Each ratio is a {value, unit, category, reason} entry; a response-level lineage (DerivedLineage) envelope marks the values pipeline-derived and points to get_company_fundamentals / verify_fact_lineage for filing-level provenance. Use the returned value exactly — do not recompute it; a null value carries a reason (e.g. INPUT_MISSING, DENOMINATOR_NEGATIVE) so missing is never confused with a real zero. Available on all plans.. It is categorised as a Read tool in the Valuein — SEC EDGAR Fundamentals & Smart-Money Data MCP Server, which means it retrieves data without modifying state.
Register the Valuein — SEC EDGAR Fundamentals & Smart-Money Data MCP server in PolicyLayer and add a rule for get_financial_ratios: 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 Valuein — SEC EDGAR Fundamentals & Smart-Money Data. Nothing to install.
get_financial_ratios 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_financial_ratios 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_financial_ratios. 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_financial_ratios is provided by the Valuein — SEC EDGAR Fundamentals & Smart-Money Data MCP server (https://mcp.valuein.biz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 68 Valuein — SEC EDGAR Fundamentals & Smart-Money Data tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.