export_client_data

Export all data for a specific client: quotes, contracts, invoices, bookings, deliveries, and projects. Returns a JSON bundle. Use for client data requests, handoffs, or PIPEDA compliance.

SERVERBusinys SOURCE@businys/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/app-businys-mcp-server/export-client-data.md

WHAT IT DOES

What export_client_data does on Businys

AI agents call export_client_data 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.

RISK

Why export_client_data is rated Low

The tool retrieves and bundles existing client data into a JSON export without modifying or deleting anything. It is a read operation. Severity is medium because it aggregates sensitive personal and financial records for a client (PII, contracts, invoices), meaning misuse could expose confidential data at scale.

From the tool's definition Export all data for a specific client: quotes, contracts, invoices, bookings, deliveries, and projects. Returns a JSON bundle.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_client_data 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_client_data, this is the rule to start with:

export_client_data Allowed

export_client_data is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_client_data": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every export_client_data call is checked against it from then on.

FAQ

Questions about export_client_data

What does the export_client_data tool do? +

Export all data for a specific client: quotes, contracts, invoices, bookings, deliveries, and projects. Returns a JSON bundle. Use for client data requests, handoffs, or PIPEDA compliance. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_client_data? +

Register the Businys MCP server in PolicyLayer and add a rule for export_client_data: 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.

What risk level is export_client_data? +

export_client_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit export_client_data? +

Yes. Add a rate_limit block to the export_client_data 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.

How do I block export_client_data completely? +

Set action: deny in the PolicyLayer policy for export_client_data. 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.

What MCP server provides export_client_data? +

export_client_data 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.

KEEP EXPLORING

More on Businys, and thousands of servers like it.

This server

All 248 Businys tools →

Across the catalogue

collect_devtools_data on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →