clio_create_company_contact
AI agents use clio_create_company_contact to create or update resources in Clio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clio environment.
This tool creates a new company contact record in Clio Manage, which is a reversible write operation. It modifies data by adding a new record but does not irreversibly delete data (would be Destructive) or move money (would be Financial).
From the tool's definition Tool name 'clio_create_company_contact' and server description states the MCP server 'enables Claude and other MCP clients to read and write Clio data including contacts, matters, and activities directly from chat.' The 'create' prefix indicates data creation.
Documented attack patterns abuse exactly the kind of access clio_create_company_contact gives an agent:
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_create_company_contact:
{
"version": "1",
"default": "deny",
"tools": {
"clio_create_company_contact": {
"limits": [
{
"counter": "clio_create_company_contact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} clio_create_company_contact stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
clio_create_company_contact. It is categorised as a Write tool in the Clio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clio MCP server in PolicyLayer and add a rule for clio_create_company_contact: 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.
clio_create_company_contact is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the clio_create_company_contact 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_create_company_contact. 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_create_company_contact 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.
Start from Clio, 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.
10 Clio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.