Create a public export job for Sanka records. Use this for integration exports such as deals to HubSpot. For invoice accounting sync to freee, MoneyForward, Xero, or QuickBooks, use preview_workflow/start_workflow with workflow_type=invoice_export instead.
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.
This tool performs a write-class operation by creating export jobs that initiate data processing pipelines. While it doesn't directly delete or destroy data (Destructive), nor does it execute arbitrary code (Execute), it does create new export records/jobs and triggers external integrations.
From the tool's definition Tool creates a public export job for records, as stated in 'Create a public export job for Sanka records.' The tool initiates an export process that generates or modifies export state/jobs, which is a write operation.
Attacks that exploit this kind of access
Create a public export job for Sanka records. Use this for integration exports such as deals to HubSpot. For invoice accounting sync to freee, MoneyForward, Xero, or QuickBooks, use preview_workflow/start_workflow with workflow_type=invoice_export instead. 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.
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 →