Insert a new record into a table
AI agents use create to create or update resources in Bun Database MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bun Database MCP Server environment.
The 'create' tool performs a reversible write operation—inserting new records into a database table. This falls squarely in the Write category: it modifies data but does not delete, destroy, or execute arbitrary code. Severity is medium because misuse could corrupt or pollute a database with unwanted records, but the impact is bounded to new inserts and can be remedied by deletion.
From the tool's definition Tool name 'create' and description 'Insert a new record into a table' indicate data creation/modification without deletion or destruction.
Attacks that exploit this kind of access
Insert a new record into a table. It is categorised as a Write tool in the Bun Database MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bun Database MCP Server MCP server in PolicyLayer and add a rule for create: 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 Bun Database MCP Server. Nothing to install.
create 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 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. 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 is provided by the Bun Database MCP Server MCP server (ross-jill-ws/bun-db-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 →