create_consulting_document_revision
Create a revision-safe proposal or SOW draft on an owned engagement.
This record as markdown: /tools/com-meta-council-decision-intelligence/create-consulting-document-revision.md
What create_consulting_document_revision does on Meta Council
AI agents use create_consulting_document_revision 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 |
|---|---|---|---|
body | string | Yes | |
kind | string | Yes | |
title | string | Yes | |
engagement_id | string | Yes | |
expected_latest_revision | integer | — |
Parameters from the server's own tool schema.
Why create_consulting_document_revision is rated Medium
This tool creates new consulting documents (proposals, statements of work) in a reversible manner. It modifies business data by adding document revisions, but does not execute code, delete data, or commit financial obligations. The 'revision-safe' qualifier suggests version control that allows rollback.
From the tool's definition Tool name 'create_consulting_document_revision' and description 'Create a revision-safe proposal or SOW draft on an owned engagement' explicitly indicate creation of new document revisions.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs create_consulting_document_revision 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_document_revision, this is the rule to start with:
create_consulting_document_revision 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_document_revision call is checked against it from then on.
Questions about create_consulting_document_revision
Create a revision-safe proposal or SOW draft on an owned 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.
create_consulting_document_revision accepts 5 parameters: body, kind, title, engagement_id, expected_latest_revision. Required: body, kind, title, 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 create_consulting_document_revision: 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_document_revision 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_document_revision 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_document_revision. 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_document_revision 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