Get the full schema of a Coda document: all tables with their columns, types, and formulas in a single call. Equivalent to running coda_list_tables + coda_list_columns for every table at once. Especially useful to understand table structure before writing data or debugging formulas. Args: - doc_i...
AI agents call coda_get_doc_schema to retrieve information from Coda MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that retrieves metadata about document structure (tables, columns, types, formulas). It has no side effects and cannot modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only discover what data structures exist, not access sensitive data values or modify anything. This falls squarely into the Read category with low severity.
From the tool's definition The tool description explicitly states it 'Get[s] the full schema of a Coda document' and is described as equivalent to list operations. The name contains 'get' and the purpose is to 'understand table structure' without modification.
Attacks that exploit this kind of access
Get the full schema of a Coda document: all tables with their columns, types, and formulas in a single call. Equivalent to running coda_list_tables + coda_list_columns for every table at once. Especially useful to understand table structure before writing data or debugging formulas. Args: - doc_id (string): The document ID - response_format:. It is categorised as a Read tool in the Coda MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Coda MCP Server MCP server in PolicyLayer and add a rule for coda_get_doc_schema: 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 MCP Server. Nothing to install.
coda_get_doc_schema 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 coda_get_doc_schema 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 coda_get_doc_schema. 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.
coda_get_doc_schema is provided by the Coda MCP Server MCP server (thierryvm/coda-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →