AI agents use insert to create or update resources in Pgmcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pgmcp environment.
INSERT is a reversible write operation that creates new data rows. While not destructive (data can be updated or deleted), it modifies the database state. Medium severity reflects that misuse could corrupt data or insert malicious records, but the operation is not irreversible.
From the tool's definition Tool named 'insert' on a PostgreSQL administration server. The name strongly indicates INSERT operations that create or modify data in a database.
Attacks that exploit this kind of access
insert. It is categorised as a Write tool in the Pgmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pg MCP server in PolicyLayer and add a rule for insert: 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 Pgmcp. Nothing to install.
insert 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 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. 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 is provided by the Pg MCP server (veloper/pgmcp). 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 →