create_consulting_client
Create an account-private consulting client.
This record as markdown: /tools/com-meta-council-decision-intelligence/create-consulting-client.md
What create_consulting_client does on Meta Council
AI agents use create_consulting_client to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
notes | string | — | |
status | string | — | |
contact_name | string | — | |
external_ref | string | — | |
organization | string | — | |
contact_email | string | — |
Parameters from the server's own tool schema.
Why create_consulting_client is rated Medium
This tool creates a new consulting client account, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. While it has moderate impact (creates a new client relationship), the action is modifiable and the scope is limited to account-private records.
From the tool's definition Tool name 'create_consulting_client' and description 'Create an account-private consulting client' indicate creation of a new record that modifies the consulting client database.
Attacks that exploit this kind of access
The rule that runs create_consulting_client safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_consulting_client, this is the rule to start with:
create_consulting_client 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every create_consulting_client call is checked against it from then on.
Questions about create_consulting_client
Create an account-private consulting client. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_consulting_client accepts 7 parameters: name, notes, status, contact_name, external_ref, organization, contact_email. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for create_consulting_client: 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 Meta Council. Nothing to install.
create_consulting_client 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 create_consulting_client 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 create_consulting_client. 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.
create_consulting_client is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue