Medium Risk

edit_table_cell

Edit table cell content Parameters: - table_index: Table index - row_index: Row index - col_index: Column index - text: Cell text

How to control edit_table_cell ↓

What edit_table_cell does on Doc/docx

AI agents use edit_table_cell to create or update resources in Doc/docx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doc/docx environment.

Medium Risk

Why edit_table_cell needs a policy

This tool modifies existing document data (table cells) reversibly. Users can undo edits or overwrite with different content, so it does not meet the Destructive threshold. It performs no I/O beyond the document itself, no code execution, and no financial impact. Write is the appropriate category as it creates or modifies data reversibly.

From the tool's definition edit_table_cell modifies table cell content by taking table_index, row_index, col_index, and text parameters. The description states it 'Edit table cell content,' which is a modification operation.

Documented attack patterns abuse exactly the kind of access edit_table_cell gives an agent:

How to control edit_table_cell

PolicyLayer is an MCP gateway — it sits between your AI agents and Doc/docx, and nothing reaches the server without passing your rules. This is the rule we recommend for edit_table_cell:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "edit_table_cell": {
      "limits": [
        {
          "counter": "edit_table_cell_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

edit_table_cell 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.

  1. Create a free account and register Doc/docx — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about edit_table_cell

What does the edit_table_cell tool do? +

Edit table cell content Parameters: - table_index: Table index - row_index: Row index - col_index: Column index - text: Cell text. It is categorised as a Write tool in the Doc/docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on edit_table_cell? +

Register the Doc/docx MCP server in PolicyLayer and add a rule for edit_table_cell: 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 Doc/docx. Nothing to install.

What risk level is edit_table_cell? +

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

Can I rate-limit edit_table_cell? +

Yes. Add a rate_limit block to the edit_table_cell 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 edit_table_cell completely? +

Set action: deny in the PolicyLayer policy for edit_table_cell. 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 edit_table_cell? +

edit_table_cell is provided by the Doc/docx MCP server (meterlong/mcp-doc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Doc/docx tool call.

Start from Doc/docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

23 Doc/docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.