export_account
Export all account data as a ZIP file containing JSON data and uploaded assets.
This record as markdown: /tools/app-businys-mcp-server/export-account.md
What export_account does on Businys
AI agents call export_account to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why export_account is rated Low
This tool reads and packages all account data into a ZIP file for export. It does not modify, delete, or execute anything — it retrieves existing data. However, the blast radius is medium because it exports ALL account data (clients, invoices, contracts, assets), which could expose sensitive business and personal information if misused by an AI agent.
From the tool's definition Export all account data as a ZIP file containing JSON data and uploaded assets
Attacks that exploit this kind of access
The rule that runs export_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For export_account, this is the rule to start with:
export_account is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every export_account call is checked against it from then on.
Questions about export_account
Export all account data as a ZIP file containing JSON data and uploaded assets. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for export_account: 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 Businys. Nothing to install.
export_account 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 export_account 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 export_account. 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.
export_account is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue