Bulk upsert by (name): for each item with keys {name, price, stock},
AI agents use product_bulk_upsert to create or update resources in Database MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Database MCP Server environment.
This tool creates or modifies product records in bulk, which is a Write operation. Severity is high because bulk operations can affect many records simultaneously, creating significant blast radius if an AI agent executes this with malformed or adversarial data (e.g., zeroing all prices or stock levels).
From the tool's definition Tool name 'product_bulk_upsert' indicates bulk upsert operations. Description states 'for each item with keys {name, price, stock}' which confirms it modifies product data (price and stock are mutable fields).
Attacks that exploit this kind of access
Bulk upsert by (name): for each item with keys {name, price, stock},. It is categorised as a Write tool in the Database MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Database MCP Server MCP server in PolicyLayer and add a rule for product_bulk_upsert: 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 Database MCP Server. Nothing to install.
product_bulk_upsert 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 product_bulk_upsert 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 product_bulk_upsert. 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.
product_bulk_upsert is provided by the Database MCP Server MCP server (vrushil1/database-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 →