export_records
Create a public export job for Sanka records. Use this for integration exports such as deals to HubSpot. For Invoice accounting sync, use preview_workflow/start_workflow with workflow_type=invoice_export; for QuickBooks Online Bill sync, use workflow_type=bill_export. Integration exports are vali...
This record as markdown: /tools/sankahq-sanka-mcp/export-records.md
What export_records does on Sanka MCP Server
AI agents use export_records to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.
Why export_records is rated Medium
This tool initiates export jobs that push data to external platforms (HubSpot, QuickBooks Online, etc.), constituting a write operation with side effects on third-party systems. While reversible (exports can be re-run or corrected), the action modifies external business systems and integrations, making it Write rather than Read.
From the tool's definition Tool creates a public export job for records (e.g., 'deals to HubSpot', 'invoice_export', 'bill_export'), which modifies external systems and integrations by exporting data.
Attacks that exploit this kind of access
The rule that runs export_records safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For export_records, this is the rule to start with:
export_records stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every export_records call is checked against it from then on.
Questions about export_records
Create a public export job for Sanka records. Use this for integration exports such as deals to HubSpot. For Invoice accounting sync, use preview_workflow/start_workflow with workflow_type=invoice_export; for QuickBooks Online Bill sync, use workflow_type=bill_export. Integration exports are validated against the runnable delivery matrix; provider/object pairs without a working native delivery pipeline are rejected with HTTP 400 and error code INTEGRATION_EXPORT_NOT_SUPPORTED (do not retry those pairs), and HTTP 503 with error code JOB_QUEUE_UNAVAILABLE means the dispatch queue is temporarily unavailable — retry later. Accepted integration exports return status. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for export_records: 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 Sanka MCP Server. Nothing to install.
export_records 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 export_records 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_records. 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_records is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue