Get detailed metadata about a specific page by its ID or name
AI agents call get_page 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.
This tool retrieves metadata about a page—a read-only operation with no side effects, no state changes, and no irreversible actions. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because exposure of page metadata alone poses minimal risk; an AI agent retrieving page details cannot corrupt data or trigger unintended external effects.
From the tool's definition Tool name 'get_page' and description 'Get detailed metadata about a specific page by its ID or name' indicate retrieval of page information without modification.
Documented attack patterns abuse exactly the kind of access get_page 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 get_page:
{
"version": "1",
"default": "deny",
"tools": {
"get_page": {}
}
}get_page is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed metadata about a specific page by its ID or name. It is categorised as a Read tool in the Coda MCP Server, which means it retrieves data without modifying state.
Register the Coda MCP server in PolicyLayer and add a rule for get_page: 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.
get_page 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 get_page 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 get_page. 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.
get_page 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.