Insert or update rows in a Coda table (base table only, not views). Provide row data as an array of objects, each with column IDs as keys. Use coda_list_columns to get the column IDs first. Args: - doc_id (string): The document ID - table_id (string): The BASE table ID (not a view) - rows (array)...
AI agents use coda_upsert_rows to create or update resources in Coda MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coda MCP Server environment.
This tool creates or modifies data (rows in a table) but does not delete data irreversibly, nor does it execute arbitrary code. It falls squarely in the Write category. Severity is medium because while the changes are reversible (rows can be edited or deleted separately), an AI agent could still cause data corruption or unintended modifications to collaborative documents that other users depend on.
From the tool's definition Tool performs insert or update operations on rows in a Coda table. The description explicitly states "Insert or update rows" which are reversible write operations that modify existing data or add new data without permanent deletion.
Attacks that exploit this kind of access
Insert or update rows in a Coda table (base table only, not views). Provide row data as an array of objects, each with column IDs as keys. Use coda_list_columns to get the column IDs first. Args: - doc_id (string): The document ID - table_id (string): The BASE table ID (not a view) - rows (array): Array of row objects. Each object has a. It is categorised as a Write tool in the Coda MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coda MCP Server MCP server in PolicyLayer and add a rule for coda_upsert_rows: 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 Coda MCP Server. Nothing to install.
coda_upsert_rows 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 coda_upsert_rows 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 coda_upsert_rows. 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.
coda_upsert_rows is provided by the Coda MCP Server MCP server (thierryvm/coda-mcp-server). 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 →