Update fields on an order (e.g., quantity or status if present).
AI agents use order_update 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 data reversibly by updating order fields such as quantity or status. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or move money (Financial). The blast radius is medium because incorrect updates could affect order fulfillment workflows, but changes are reversible through subsequent updates.
From the tool's definition Tool name 'order_update' and description 'Update fields on an order (e.g., quantity or status if present)' indicate modification of existing data records.
Attacks that exploit this kind of access
Update fields on an order (e.g., quantity or status if present). 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 order_update: 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.
order_update 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 order_update 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 order_update. 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.
order_update 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 →