Calls GET /users/who_am_i.json to confirm credentials work and return the current user record.
AI agents call clio_who_am_i to retrieve information from Clio Manage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns the current authenticated user's profile information. It has no side effects—it neither creates, modifies, deletes, nor executes operations. It is purely informational, making it a Read category risk.
From the tool's definition Tool description states it 'Calls GET /users/who_am_i.json to confirm credentials work and return the current user record.' GET is a read-only HTTP verb; returns identity information without modification.
Attacks that exploit this kind of access
Calls GET /users/who_am_i.json to confirm credentials work and return the current user record. It is categorised as a Read tool in the Clio Manage MCP MCP Server, which means it retrieves data without modifying state.
Register the Clio Manage MCP server in PolicyLayer and add a rule for clio_who_am_i: 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 Clio Manage MCP. Nothing to install.
clio_who_am_i 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 clio_who_am_i 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 clio_who_am_i. 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.
clio_who_am_i is provided by the Clio Manage MCP server (patrickking67/clio-manage-mcp). 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 →