update_row · Retable MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_row does on Retable MCP Server

AI agents use update_row to create or update resources in Retable MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Retable MCP Server environment.

WHY IT NEEDS A POLICY

Why update_row needs a policy

This tool modifies data (updates a row) but does not delete or irreversibly destroy it, so it is Write rather than Destructive. The severity is medium because an AI agent misusing this tool could corrupt or alter important data within a table, affecting data integrity and business logic, but the change is theoretically reversible through another update or rollback.

From the tool's definition Tool name 'update_row' and description 'Update an existing row in a specific Retable' indicate modification of data. The verb 'update' is explicitly a write operation that changes existing data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_row Rate-limited

update_row stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_row": {
      "limits": [
        {
          "counter": "update_row_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Retable MCP Server, so you can run agents against it safely.

FAQ

Questions about update_row

What does the update_row tool do? +

Update an existing row in a specific Retable. It is categorised as a Write tool in the Retable MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_row? +

Register the Retable MCP Server 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 Retable MCP Server. Nothing to install.

What risk level is update_row? +

update_row is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_row? +

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.

How do I block update_row completely? +

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.

What MCP server provides update_row? +

update_row is provided by the Retable MCP Server MCP server (retable-io/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.