Update properties of a Coda doc including title and icon
AI agents use update_doc to create or update resources in Coda — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coda environment.
This tool modifies existing document properties (title, icon) which are changeable, reversible operations. It does not execute arbitrary code, delete data, or move money. It fits the Write category—creates or modifies data reversibly.
From the tool's definition Tool name 'update_doc' and description 'Update properties of a Coda doc including title and icon' indicate modification of document metadata. The word 'Update' confirms reversible change, not deletion or destruction.
Documented attack patterns abuse exactly the kind of access update_doc 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 update_doc:
{
"version": "1",
"default": "deny",
"tools": {
"update_doc": {
"limits": [
{
"counter": "update_doc_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_doc stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update properties of a Coda doc including title and icon. It is categorised as a Write tool in the Coda MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coda MCP server in PolicyLayer and add a rule for update_doc: 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.
update_doc is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_doc 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 update_doc. 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.
update_doc 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.