AI agents use xbrl_close_filing to create or update resources in Arelle — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Arelle environment.
This tool modifies the application state by closing a filing and deallocating memory, which is a reversible operation (the filing can be reloaded). It does not delete persistent data, execute arbitrary code, move money, or permanently destroy information. The operation is similar to closing a file handle or session—a Write-category resource management action.
From the tool's definition Tool name 'xbrl_close_filing' and description 'Close a loaded filing and free its memory' indicate a state-modifying operation that closes/unloads a filing resource.
Attacks that exploit this kind of access
Close a loaded filing and free its memory (30-60MB per filing). It is categorised as a Write tool in the Arelle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Arelle MCP server in PolicyLayer and add a rule for xbrl_close_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_close_filing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the xbrl_close_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_close_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_close_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 →