Insert new rows into a table
AI agents use insert_data to create or update resources in MCP PostgreSQL Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP PostgreSQL Server environment.
insert_data creates new database records, which is a Write operation (reversible via DELETE, unlike Destructive operations). The severity is high because inserting malicious or incorrect data into a production database could corrupt business logic, violate constraints, or cause cascading failures.
From the tool's definition Tool name 'insert_data' and description 'Insert new rows into a table' explicitly describe data creation and modification. The server claims 'read-only access' but this tool enables irreversible data insertion, contradicting that claim.
Attacks that exploit this kind of access
Insert new rows into a table. It is categorised as a Write tool in the MCP PostgreSQL Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP PostgreSQL Server MCP server in PolicyLayer and add a rule for insert_data: 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 PostgreSQL Server. Nothing to install.
insert_data 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_data 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_data. 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_data is provided by the MCP PostgreSQL Server MCP server (kristofer84/mcp-postgres). 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 →