import_records · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What import_records does on Sanka MCP Server

AI agents use import_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 IT NEEDS A POLICY

Why import_records needs a policy

This tool creates new records via bulk import operations, which is a reversible data modification. While powerful and potentially high-impact (especially given the sibling tools like activate_invoice and approve_payroll_run suggest financial/operational systems), the import itself is not destructive or irreversible.

From the tool's definition 'Create a public import job' indicates the tool creates data records in bulk. The description mentions 'item CSV imports' and references to 'HubSpot Deal ids', suggesting it writes/creates business records at scale.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_records Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_records": {
      "limits": [
        {
          "counter": "import_records_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about import_records

What does the import_records tool do? +

Create a public import job. Use upload_import_file first for item CSV imports, or pass HubSpot Deal ids with object_type=. 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.

How do I enforce a policy on import_records? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for import_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.

What risk level is import_records? +

import_records is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_records? +

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

How do I block import_records completely? +

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

What MCP server provides import_records? +

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