bulk_import

Import records in bulk from CSV data. Creates companies, people, or opportunities from structured CSV input. Each row becomes a record. Custom fields are supported via column names prefixed with

SERVERAdrata SOURCE@adrata/adrata-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/bulk-import.md

WHAT IT DOES

What bulk_import does on Adrata

AI agents use bulk_import to create or update resources in Adrata, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adrata environment.

RISK

Why bulk_import is rated Medium

An AI agent can call bulk_import faster than any human can review: one bad instruction and it creates or modifies resources in Adrata by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bulk_import safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_import, this is the rule to start with:

bulk_import Rate-limited

bulk_import 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": {
    "bulk_import": {
      "limits": [
        {
          "counter": "bulk_import_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about bulk_import

What does the bulk_import tool do? +

Import records in bulk from CSV data. Creates companies, people, or opportunities from structured CSV input. Each row becomes a record. Custom fields are supported via column names prefixed with. It is categorised as a Write tool in the Adrata MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bulk_import? +

Register the Adrata MCP server in PolicyLayer and add a rule for bulk_import: 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 Adrata. Nothing to install.

What risk level is bulk_import? +

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

Can I rate-limit bulk_import? +

Yes. Add a rate_limit block to the bulk_import 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 bulk_import completely? +

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

bulk_import is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 278 Adrata tools →

Across the catalogue

sms_send_bulk on Twilio SMS MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →