Insert a new record into a table with specified data
AI agents use create_record to create or update resources in Mcp Sqlite — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Sqlite environment.
The tool creates new data in a database table, which is a reversible write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), or involve financial transactions (not Financial). While the sibling tools include delete_records and update_records, this specific tool is limited to record insertion.
From the tool's definition Tool name 'create_record' and description 'Insert a new record into a table with specified data' indicate data creation/modification. This is a write operation that creates new database records.
Attacks that exploit this kind of access
Insert a new record into a table with specified data. It is categorised as a Write tool in the Mcp Sqlite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Sqlite MCP server in PolicyLayer and add a rule for create_record: 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 Sqlite. Nothing to install.
create_record 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 create_record 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 create_record. 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.
create_record is provided by the Mcp Sqlite MCP server (mcp-sqlite). 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 →