AI agents call xbrl_fetch_sec_filing to retrieve information from Arelle without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves financial filing data from the SEC EDGAR database, which is a read-only operation with no side effects on the data. However, severity is elevated to 'medium' rather than 'low' because SEC filings contain sensitive financial and business information that could be misused if extracted at scale or combined with other tools to analyze proprietary competitor data.
From the tool's definition Tool name 'xbrl_fetch_sec_filing' indicates retrieval of SEC EDGAR filings. The server context describes 'SEC EDGAR integration' and filing operations. 'Fetch' is a retrieval verb with no modification or execution implications.
Attacks that exploit this kind of access
xbrl_fetch_sec_filing. It is categorised as a Read tool in the Arelle MCP Server, which means it retrieves data without modifying state.
Register the Arelle MCP server in PolicyLayer and add a rule for xbrl_fetch_sec_filing: 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 Arelle. Nothing to install.
xbrl_fetch_sec_filing 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 xbrl_fetch_sec_filing 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 xbrl_fetch_sec_filing. 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.
xbrl_fetch_sec_filing is provided by the Arelle MCP server (thekinghippopotamus/arelle-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 →