get_record_history

THE RISK

Low Risk

Why get_record_history needs a policy

This tool retrieves audit/changelog data about a record's past modifications. It queries existing information without creating, modifying, deleting, executing code, or committing financial transactions. The read-only nature and historical scope present minimal risk—the worst outcome is information disclosure about changes that already occurred within the database.

From the tool's definition Tool name 'get_record_history' and description 'Get history of changes for a specific record' indicate a retrieval operation. The verb 'get' and the focus on querying historical data without modification confirm this is a read-only action.

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

POLICY

How to control get_record_history

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_record_history": {}
  }
}

get_record_history is read-only, so it stays allowed — but 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.

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

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_record_history

What does the get_record_history tool do? +

Get history of changes for a specific record. It is categorised as a Read tool in the Teable MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_record_history? +

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

get_record_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_record_history? +

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

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

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