AI agents call xbrl_compare_filings 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.
Comparison of filings is fundamentally a read operation that retrieves and analyzes data without modifying, deleting, or executing arbitrary code. The sibling tools on this server (xbrl_browse_taxonomy, xbrl_concept_details, xbrl_company_facts) are predominantly Read operations, suggesting xbrl_compare_filings follows the same pattern.
From the tool's definition Tool name 'xbrl_compare_filings' indicates a comparison operation on XBRL financial filings. No description provided, but 'compare' is a read-only analytical operation.
Attacks that exploit this kind of access
xbrl_compare_filings. 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_compare_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 Arelle. Nothing to install.
xbrl_compare_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 xbrl_compare_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 xbrl_compare_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.
xbrl_compare_filings 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 →