clio_who_am_i

THE RISK

Low Risk

Why clio_who_am_i needs a policy

The name 'who_am_i' is a classic identity/profile lookup pattern that reads the current user's information from the system. No side effects are expected. Confidence is reduced due to the empty description, but the naming convention is strongly associated with read-only identity queries.

From the tool's definition Tool name 'clio_who_am_i' suggests retrieving the current authenticated user's identity/profile information. Description is empty.

Documented attack patterns abuse exactly the kind of access clio_who_am_i gives an agent:

POLICY

How to control clio_who_am_i

PolicyLayer is an MCP gateway — it sits between your AI agents and Clio, and nothing reaches the server without passing your rules. This is the rule we recommend for clio_who_am_i:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clio_who_am_i": {}
  }
}

clio_who_am_i is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Clio — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Clio tools

Destructive clio_delete_contact clio_delete_contact Destructive clio_delete_matter clio_delete_matter Execute clio_api_request clio_api_request Write clio_create_company_contact clio_create_company_contact Write clio_create_flat_fee_activity clio_create_flat_fee_activity Write clio_create_matter clio_create_matter Write clio_create_person_contact clio_create_person_contact Read clio_find_contact clio_find_contact

All 10 Clio tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clio_who_am_i

What does the clio_who_am_i tool do? +

clio_who_am_i. It is categorised as a Read tool in the Clio MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on clio_who_am_i? +

Register the Clio 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. Nothing to install.

What risk level is clio_who_am_i? +

clio_who_am_i is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit clio_who_am_i? +

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.

How do I block clio_who_am_i completely? +

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.

What MCP server provides clio_who_am_i? +

clio_who_am_i is provided by the Clio MCP server (lawyered0/clio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clio tool call.

Start from Clio, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →