Enable or disable public share link for a view. Returns the share URL when enabled.
AI agents use share_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.
This tool modifies the sharing state of a view (enabling or disabling public access), which is a reversible write operation. However, it carries high severity because enabling a public share link could expose potentially sensitive database content to anyone with the URL, representing a significant data exposure risk if misused by an AI agent.
From the tool's definition Enable or disable public share link for a view. Returns the share URL when enabled.
Documented attack patterns abuse exactly the kind of access share_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 share_view:
{
"version": "1",
"default": "deny",
"tools": {
"share_view": {
"limits": [
{
"counter": "share_view_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} share_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.
Enable or disable public share link for a view. Returns the share URL when enabled. 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 share_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.
share_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 share_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 share_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.
share_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.