update_consulting_engagement
Update mutable fields on an owned consulting engagement.
This record as markdown: /tools/com-meta-council-decision-intelligence/update-consulting-engagement.md
What update_consulting_engagement does on Meta Council
AI agents use update_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 | — | |
status | string | — | |
client_id | string | — | |
objective | string | — | |
start_date | string | — | |
engagement_id | string | Yes | |
sales_deal_ref | string | — | |
target_end_date | string | — | |
accounting_run_ref | string | — |
Parameters from the server's own tool schema.
Why update_consulting_engagement is rated Medium
The tool modifies consulting engagement records (a form of structured business data) reversibly. Updates can be undone by subsequent updates or version control. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).
From the tool's definition Tool name includes 'update' and description states 'Update mutable fields on an owned consulting engagement.' This directly indicates modification of existing data.
Attacks that exploit this kind of access
The rule that runs update_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 update_consulting_engagement, this is the rule to start with:
update_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 update_consulting_engagement call is checked against it from then on.
Questions about update_consulting_engagement
Update mutable fields on an owned consulting engagement. 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.
update_consulting_engagement accepts 9 parameters: title, status, client_id, objective, start_date, engagement_id, sales_deal_ref, target_end_date, accounting_run_ref. Required: engagement_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 update_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.
update_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 update_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 update_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.
update_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