Import a CSV file to seekdb. Args: filePath: The path to the CSV file. The file must have a header row. columnNumberForVecotor: Optional. The column number (1-started) to use as the document for vector embedding. If specified, creates a vector collection with this column as documents and others a...
AI agents use import_csv_file_to_seekdb to create or update resources in Mcp Oceanbase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Oceanbase environment.
This tool writes data to a database by importing CSV contents into either a vector collection or a MySQL table. The operation is reversible (the imported data can be deleted or the table dropped), making it Write rather than Destructive.
From the tool's definition Import a CSV file to seekdb... creates a vector collection... creates a regular MySQL table
Documented attack patterns abuse exactly the kind of access import_csv_file_to_seekdb gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Oceanbase, and nothing reaches the server without passing your rules. This is the rule we recommend for import_csv_file_to_seekdb:
{
"version": "1",
"default": "deny",
"tools": {
"import_csv_file_to_seekdb": {
"limits": [
{
"counter": "import_csv_file_to_seekdb_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_csv_file_to_seekdb 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.
Free to start. No card required.
Import a CSV file to seekdb. Args: filePath: The path to the CSV file. The file must have a header row. columnNumberForVecotor: Optional. The column number (1-started) to use as the document for vector embedding. If specified, creates a vector collection with this column as documents and others as metadata. If not specified, creates a regular MySQL table with inferred column types. Returns: A JSON string indicating success or error. It is categorised as a Write tool in the Mcp Oceanbase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for import_csv_file_to_seekdb: 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 Mcp Oceanbase. Nothing to install.
import_csv_file_to_seekdb 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 import_csv_file_to_seekdb 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 import_csv_file_to_seekdb. 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.
import_csv_file_to_seekdb is provided by the Mcp Oceanbase MCP server (oceanbase/awesome-oceanbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 134 Mcp Oceanbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
134 Mcp Oceanbase tools catalogued and risk-classified — across an index of 42,500+ MCP servers.