comment_on_record

THE RISK

Medium Risk

Why comment_on_record needs a policy

Posting a comment creates new content but does not modify or delete existing records, making it a Write operation. The action is reversible (comments can be deleted). Severity is low because comments are typically low-impact metadata with minimal blast radius, and the operation does not affect core data integrity or business-critical records.

From the tool's definition Tool description states 'Post a comment on a specific record' — this creates new data (a comment) in the database in a reversible manner.

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

POLICY

How to control comment_on_record

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

policy.json

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

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

Create a free account and register Teable MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Teable MCP Server tools

Destructive delete_field Permanently delete a field from a table (all data in this field will be lost) Destructive delete_record Permanently delete a record (all data will be lost). This operation is irreversible. Destructive delete_table Delete a table (moves to trash, recoverable via restore_table_from_trash) Destructive delete_view Delete a view from a table Destructive permanently_delete_table Permanently and irreversibly delete a table. This cannot be undone. The table must already Write share_view Enable or disable public share link for a view. Returns the share URL when enabled. Write create_field Create a new field in a table Write create_record Create a new record in a table

All 29 Teable MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about comment_on_record

What does the comment_on_record tool do? +

Post a comment on a specific record. It is categorised as a Write tool in the Teable 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 comment_on_record? +

Register the Teable MCP Server MCP server in PolicyLayer and add a rule for comment_on_record: 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 Teable MCP Server. Nothing to install.

What risk level is comment_on_record? +

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

Can I rate-limit comment_on_record? +

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

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

comment_on_record is provided by the Teable MCP Server MCP server (ltphat2204/teable-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Teable MCP Server tool call.

Start from Teable MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →