create_consulting_engagement
Create an engagement for an owned consulting client.
This record as markdown: /tools/com-meta-council-decision-intelligence/create-consulting-engagement.md
What create_consulting_engagement does on Meta Council
AI agents use create_consulting_engagement 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 |
|---|---|---|---|
title | string | Yes | |
status | string | — | |
client_id | string | Yes | |
objective | string | — | |
start_date | string | — | |
external_ref | string | — | |
sales_deal_ref | string | — | |
target_end_date | string | — | |
accounting_run_ref | string | — |
Parameters from the server's own tool schema.
Why create_consulting_engagement is rated Medium
This tool creates a new consulting engagement record, which is a reversible write operation that establishes a commitment with a client. It does not execute arbitrary code, delete data irreversibly, or move money directly, but it does create structured data that modifies the business state.
From the tool's definition Tool name is 'create_consulting_engagement' and description states 'Create an engagement for an owned consulting client.' The verb 'create' and the operational context (establishing a new consulting engagement) indicate data creation with business-relevant…
Attacks that exploit this kind of access
The rule that runs create_consulting_engagement 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_engagement, this is the rule to start with:
create_consulting_engagement 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_engagement call is checked against it from then on.
Questions about create_consulting_engagement
Create an engagement for an owned 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_engagement accepts 9 parameters: title, status, client_id, objective, start_date, external_ref, sales_deal_ref, target_end_date, accounting_run_ref. Required: title, client_id. 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_engagement: 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_engagement 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_engagement 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_engagement. 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_engagement 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