Get detailed information about a specific table including its schema, columns, and metadata
AI agents call get_table to retrieve information from Coda without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a table's schema, columns, and metadata without creating, modifying, or deleting any data. It is a straightforward read operation with no side effects. The blast radius is minimal as misuse would only expose information already accessible to users with appropriate permissions, not cause data loss or unauthorized changes.
From the tool's definition Tool name 'get_table' and description 'Get detailed information about a specific table including its schema, columns, and metadata' indicate retrieval of table structure and metadata without modification.
Documented attack patterns abuse exactly the kind of access get_table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Coda, and nothing reaches the server without passing your rules. This is the rule we recommend for get_table:
{
"version": "1",
"default": "deny",
"tools": {
"get_table": {}
}
}get_table is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a specific table including its schema, columns, and metadata. It is categorised as a Read tool in the Coda MCP Server, which means it retrieves data without modifying state.
Register the Coda MCP server in PolicyLayer and add a rule for get_table: 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 Coda. Nothing to install.
get_table is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_table 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 get_table. 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.
get_table is provided by the Coda MCP server (tjc-lp/coda-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Coda, 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.
24 Coda tools catalogued and risk-classified — across an index of 43,000+ MCP servers.