edgar-get-company-facts
Fetch all XBRL-tagged facts for a single company (full company-facts payload).
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/edgar-get-company-facts.md
What edgar-get-company-facts does on Meta Data Mcp
AI agents call edgar-get-company-facts to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why edgar-get-company-facts is rated Low
This tool retrieves publicly available SEC EDGAR data (XBRL-formatted financial facts) for a company. It is a read-only query operation against open financial data with no side effects, data modification, execution, destruction, or financial transaction capabilities. The blast radius of misuse is minimal—an attacker could only access or exfiltrate already-public company financial disclosures.
From the tool's definition Tool name 'edgar-get-company-facts' with description 'Fetch all XBRL-tagged facts for a single company' uses 'Fetch' which is a retrieval operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs edgar-get-company-facts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For edgar-get-company-facts, this is the rule to start with:
edgar-get-company-facts 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 Meta Data Mcp, apply this rule, and every edgar-get-company-facts call is checked against it from then on.
Questions about edgar-get-company-facts
Fetch all XBRL-tagged facts for a single company (full company-facts payload). It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for edgar-get-company-facts: 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 Meta Data Mcp. Nothing to install.
edgar-get-company-facts 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 edgar-get-company-facts 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 edgar-get-company-facts. 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.
edgar-get-company-facts is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue