This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/coda-list-rows.md
What coda_list_rows does on UnClick
AI agents call coda_list_rows to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Rows to return (max 200, default 25) |
doc_id | string | Yes | Coda doc id |
table_id | string | Yes | Coda table id or name |
api_token | string | Yes | Coda API token |
Parameters from the server's own tool schema.
Why coda_list_rows is rated Low
This tool retrieves or queries existing data from a Coda table with no side effects. It does not create, modify, delete, or execute operations. The minimal blast radius of misuse is accidental exposure of sensitive data already accessible to the authenticated user, typical of read-only operations.
From the tool's definition Tool name 'coda_list_rows' and description 'List rows in a Coda table' clearly indicate data retrieval without modification. The verb 'list' is a quintessential read operation.
Attacks that exploit this kind of access
The rule that runs coda_list_rows safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coda_list_rows, this is the rule to start with:
coda_list_rows is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every coda_list_rows call is checked against it from then on.
Questions about coda_list_rows
List rows in a Coda table. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
coda_list_rows accepts 4 parameters: limit, doc_id, table_id, api_token. Required: doc_id, table_id, api_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for coda_list_rows: 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 UnClick. Nothing to install.
coda_list_rows 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_list_rows 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_list_rows. 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_list_rows is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue