Get information about the current authenticated Coda user including name, email, and scoped token info
AI agents call whoami 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 read-only information about the authenticated user. It performs no data manipulation, deletion, code execution, or financial operations. The information returned (name, email, token info) are identity attributes that are safe to expose. Blast radius is minimal—an AI agent calling this tool would only learn user identity details without ability to modify data or perform privileged actions.
From the tool's definition Tool name 'whoami' and description 'Get information about the current authenticated Coda user including name, email, and scoped token info' indicates retrieval of user identity and authentication metadata with no modification or side effects.
Documented attack patterns abuse exactly the kind of access whoami 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 whoami:
{
"version": "1",
"default": "deny",
"tools": {
"whoami": {}
}
}whoami 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 information about the current authenticated Coda user including name, email, and scoped token info. 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 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. Nothing to install.
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 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 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.
whoami 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.