Low Risk

get_column

Get detailed information about a specific column including its type, format, and formula

How to control get_column ↓

What get_column does on Coda

AI agents call get_column 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.

Low Risk

Why get_column needs a policy

This tool retrieves column metadata (type, format, formula details) from a Coda document without creating, modifying, deleting, or executing operations. It is a read-only query operation with minimal blast radius if misused by an AI agent—the worst outcome would be disclosure of column structure information.

From the tool's definition Tool name 'get_column' and description 'Get detailed information about a specific column' indicates retrieval of metadata without modification or execution of side effects.

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

How to control get_column

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_column": {}
  }
}

get_column is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Coda — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_column

What does the get_column tool do? +

Get detailed information about a specific column including its type, format, and formula. It is categorised as a Read tool in the Coda MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_column? +

Register the Coda MCP server in PolicyLayer and add a rule for get_column: 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.

What risk level is get_column? +

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

Can I rate-limit get_column? +

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

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

get_column 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.

Enforce policy on every Coda tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.