update_consulting_deliverable
Edit an internal draft deliverable; review/approval state is separate.
This record as markdown: /tools/com-meta-council-decision-intelligence/update-consulting-deliverable.md
What update_consulting_deliverable does on Meta Council
AI agents use update_consulting_deliverable 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 | — | |
due_date | string | — | |
description | string | — | |
milestone_id | string | — | |
deliverable_id | string | Yes |
Parameters from the server's own tool schema.
Why update_consulting_deliverable is rated Medium
This tool creates or modifies data in a reversible manner (editing internal drafts). It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or retrieve without side effects (Read).
From the tool's definition The tool name and description indicate it 'Edit[s] an internal draft deliverable,' which modifies existing data. The phrase 'review/approval state is separate' confirms this is reversible content modification rather than deletion or approval action.
Attacks that exploit this kind of access
The rule that runs update_consulting_deliverable 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_deliverable, this is the rule to start with:
update_consulting_deliverable 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_deliverable call is checked against it from then on.
Questions about update_consulting_deliverable
Edit an internal draft deliverable; review/approval state is separate. 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_deliverable accepts 5 parameters: title, due_date, description, milestone_id, deliverable_id. Required: deliverable_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_deliverable: 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_deliverable 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_deliverable 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_deliverable. 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_deliverable 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