Retrieve information about the currently authenticated Coda user. Useful to verify which account is active and confirm the API token is valid. Args: - response_format:
AI agents call coda_whoami 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 retrieves metadata about the authenticated user (verification of account and API token validity) with no ability to modify, delete, execute code, or affect financial systems. It is a straightforward read-only authentication check with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'coda_whoami' and description 'Retrieve information about the currently authenticated Coda user' indicates a query operation that returns user identity data without modification or side effects.
Attacks that exploit this kind of access
Retrieve information about the currently authenticated Coda user. Useful to verify which account is active and confirm the API token is valid. Args: - 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_whoami: 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_whoami 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_whoami 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_whoami. 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_whoami 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 →