List and search Coda documents accessible by the API token. Returns doc titles, IDs, owner, creation dates and URLs. Args: - query (string, optional): Filter by title keywords - limit (number): Max docs to return, 1–500 (default 25) - page_token (string, optional): Pagination token from previous ...
AI agents call coda_list_docs 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 tool performs a retrieval operation on Coda documents with optional filtering and pagination. It has no side effects, does not modify data, and returns metadata about accessible documents. This is a standard read operation with minimal security risk. The blast radius of misuse is low—an agent could retrieve information about available documents but cannot alter, delete, or execute actions.
From the tool's definition Tool description states it 'List and search Coda documents' and 'Returns doc titles, IDs, owner, creation dates and URLs.' The arguments are query filters, limit, and pagination—all consistent with read-only retrieval.
Attacks that exploit this kind of access
List and search Coda documents accessible by the API token. Returns doc titles, IDs, owner, creation dates and URLs. Args: - query (string, optional): Filter by title keywords - limit (number): Max docs to return, 1–500 (default 25) - page_token (string, optional): Pagination token from previous response - 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_list_docs: 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_list_docs 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_docs 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_docs. 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_docs 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 →