db_import
Bulk import rows into a table. Up to 10,000 rows per request. Values are auto-converted to strings (sqld requirement). Much faster than db_exec for large inserts.
This record as markdown: /tools/cloud-easybits-easybits/db-import.md
What db_import does on EasyBits
AI agents use db_import to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why db_import is rated Medium
Bulk import modifies database state reversibly but affects up to 10,000 rows, creating significant data integrity risk.
From the tool's definition Bulk import rows into a table, auto-converted to strings
Attacks that exploit this kind of access
The rule that runs db_import safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For db_import, this is the rule to start with:
db_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.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every db_import call is checked against it from then on.
Questions about db_import
Bulk import rows into a table. Up to 10,000 rows per request. Values are auto-converted to strings (sqld requirement). Much faster than db_exec for large inserts. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for db_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 EasyBits. Nothing to install.
db_import 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 db_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.
Set action: deny in the PolicyLayer policy for db_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.
db_import is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue