AI agents call xbrl_fact_details 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.
Based on naming convention and context within the server's sibling tools, this tool appears to retrieve or query detailed information about XBRL financial filing facts without modifying data. The 'fact_details' suffix indicates data retrieval rather than creation, modification, or deletion.
From the tool's definition Tool name is 'xbrl_fact_details' which follows the read pattern of other sibling tools like 'xbrl_company_facts', 'xbrl_concept_details', and 'xbrl_browse_taxonomy'. The name suggests retrieval of detailed information about XBRL facts.
Attacks that exploit this kind of access
xbrl_fact_details. 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_fact_details: 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_fact_details 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_fact_details 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_fact_details. 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_fact_details 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 →