Update specific fields of an existing row. Only the fields provided in data are updated; others are preserved. Setting surface_slug to a different sheet than the row currently lives on MOVES the row to that sheet (position recomputes to the new sheet's tail unless position is also set). Same surf...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Dock server.
Free to start. No card required.
AI agents use update_row to create or modify resources in Dock. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_row repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Dock.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"update_row": {
"limits": [
{
"counter": "update_row_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Dock policy for all 64 tools.
These attack patterns abuse exactly the kind of access update_row gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Update specific fields of an existing row. Only the fields provided in data are updated; others are preserved. Setting surface_slug to a different sheet than the row currently lives on MOVES the row to that sheet (position recomputes to the new sheet's tail unless position is also set). Same surface as current → no-op move. Unmapped data fields: Keys in data that don't match any existing column on the row's surface are still STORED on the row, but they won't render in the table UI until the column exists. The response carries an unmapped_fields array plus a human-readable warning. Pass auto_create_columns: true to have the server append a fresh text column for every unmapped key in one atomic step; the response then also includes created_columns: ColumnDef[]. Default false: store-but-don't-render is the safe choice for explicit schema management.. It is categorised as a Write tool in the Dock MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dock MCP server in PolicyLayer and add a rule for update_row: 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 Dock. Nothing to install.
update_row 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 update_row 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 update_row. 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.
update_row is provided by the Dock MCP server (https://trydock.ai/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 64 Dock tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.