Reports whether valid Clio credentials are currently available, the Clio user id they were
AI agents call clio_auth_status 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 only retrieves and reports the status of authentication credentials; it performs no modifications, deletions, executions, or financial operations. It is a read-only check that returns credential availability state, making it a Read category tool with low severity since checking auth status poses minimal risk even if misused by an agent.
From the tool's definition Tool name and description indicate it 'Reports whether valid Clio credentials are currently available' — a pure query operation with no side effects.
Attacks that exploit this kind of access
Reports whether valid Clio credentials are currently available, the Clio user id they were. 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_auth_status: 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_auth_status 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_auth_status 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_auth_status. 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_auth_status 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 →