AI agents use update_view to create or update resources in Teable MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Teable MCP Server environment.
The tool creates or modifies data reversibly by updating view definitions (filters, sorting, grouping, field visibility, etc.). This is a Write operation, not Destructive, because view modifications can be undone or reverted. Severity is medium because misuse could disrupt legitimate users' access to data through those views, but does not delete data or cause financial harm.
From the tool's definition Tool name 'update_view' explicitly indicates modification of a view. The description states 'Update a view', which is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access update_view gives an agent:
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 update_view:
{
"version": "1",
"default": "deny",
"tools": {
"update_view": {
"limits": [
{
"counter": "update_view_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_view 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.
Free to start. No card required.
Update a view. 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.
Register the Teable MCP Server MCP server in PolicyLayer and add a rule for update_view: 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.
update_view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_view 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.
Set action: deny in the PolicyLayer policy for update_view. 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.
update_view 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.
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.
Free to start. No card required.
29 Teable MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.