Insert data into a knowledge base from a source query. Supports batch processing.
AI agents use insert_kb to create or update resources in MindsDB MySQL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MindsDB MySQL MCP Server environment.
The tool inserts (creates/adds) data into a knowledge base, which is a Write operation—it modifies data but does not delete, execute arbitrary code, or move money. The batch processing capability and integration with source queries present a medium severity due to potential for bulk data injection, but this remains a reversible write operation.
From the tool's definition Tool name 'insert_kb' and description 'Insert data into a knowledge base from a source query' indicates creating/adding data to a knowledge base. This is a write operation that modifies data reversibly.
Attacks that exploit this kind of access
Insert data into a knowledge base from a source query. Supports batch processing. It is categorised as a Write tool in the MindsDB MySQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MindsDB MySQL MCP Server MCP server in PolicyLayer and add a rule for insert_kb: 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 MindsDB MySQL MCP Server. Nothing to install.
insert_kb 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 insert_kb 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 insert_kb. 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.
insert_kb is provided by the MindsDB MySQL MCP Server MCP server (nikhgupta/mindsdb-mysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →