AI agents invoke xbrl_run_formula to trigger actions in Arelle. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes formulas—a form of computation—within XBRL filings. This is Execute-category because it runs code-like operations that process arguments and produce dependent results, rather than merely reading data. Severity is high because formula execution in financial filings could produce incorrect calculated values, misleading analyses, or downstream financial decisions if exploited.
From the tool's definition Tool name 'xbrl_run_formula' indicates execution of formulas within XBRL context. Empty description prevents full certainty, but formula execution in financial filing systems constitutes running code-like operations whose effects depend on formula arguments.
Attacks that exploit this kind of access
xbrl_run_formula. It is categorised as a Execute tool in the Arelle MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Arelle MCP server in PolicyLayer and add a rule for xbrl_run_formula: 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_run_formula is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the xbrl_run_formula 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_run_formula. 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_run_formula 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 →