restore_table_from_trash

THE RISK

Medium Risk

Why restore_table_from_trash needs a policy

This tool recovers previously deleted data by restoring a table from trash. While it modifies state (undeletes a table), the operation is fundamentally reversible—the table can be deleted again. This distinguishes it from Destructive (which is irreversible). Restoring from trash is a Write operation because it creates/recovers data state.

From the tool's definition Tool name 'restore_table_from_trash' and description 'Restore a deleted table from the trash back to the active base' indicate a reversal of a prior deletion operation, making the state change reversible.

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

POLICY

How to control restore_table_from_trash

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 restore_table_from_trash:

policy.json

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

restore_table_from_trash 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 comment_on_record Post a comment on a specific record Write create_field Create a new field 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 restore_table_from_trash

What does the restore_table_from_trash tool do? +

Restore a deleted table from the trash back to the active base. First call get_table_trash to get the trashId of the item to restore. 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 restore_table_from_trash? +

Register the Teable MCP Server MCP server in PolicyLayer and add a rule for restore_table_from_trash: 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 restore_table_from_trash? +

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

Can I rate-limit restore_table_from_trash? +

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

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

restore_table_from_trash 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 →