import_csv · Fusebase MCP Server MCP: Risk & Policy

WHAT IT DOES

What import_csv does on Fusebase MCP Server

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

WHY IT NEEDS A POLICY

Why import_csv needs a policy

The tool creates new database rows from CSV content, which is a reversible write operation. While it modifies data, it does not delete or permanently destroy existing records, nor does it execute arbitrary code or move money. The severity is high due to potential for bulk data modification affecting database integrity if misused with malicious CSV content or incorrect database/view IDs.

From the tool's definition Tool description states 'Import CSV data into an existing database table/view' and 'will import the rows into the database', indicating creation/modification of data records in a database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_csv Rate-limited

import_csv 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_csv": {
      "limits": [
        {
          "counter": "import_csv_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 Fusebase MCP Server, so you can run agents against it safely.

FAQ

Questions about import_csv

What does the import_csv tool do? +

Import CSV data into an existing database table/view. Provide the CSV content, the database ID, dashboard (table) ID, and the view ID. The server will import the rows into the database. Column mapping is auto-generated from CSV headers (all imported as. It is categorised as a Write tool in the Fusebase 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_csv? +

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

What risk level is import_csv? +

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

Can I rate-limit import_csv? +

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

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

import_csv is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.