approve_consulting_document_revision

Approve and lock one exact proposal/SOW revision. Requires the separate consulting:approve scope and never publishes or shares it.

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/approve-consulting-document-revision.md

WHAT IT DOES

What approve_consulting_document_revision does on Meta Council

AI agents use approve_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
`document_id`	string	Yes
`expected_version`	integer	Yes
`expected_content_hash`	string	Yes

Parameters from the server's own tool schema.

RISK

Why approve_consulting_document_revision is rated Medium

This tool performs a state-modifying action (approval and locking) on consulting documents. While approval workflows are common business operations, the locking mechanism prevents subsequent modifications, making it a write operation with moderate blast radius—an AI agent approving wrong revisions could block legitimate document updates.

From the tool's definition Tool description states it "Approve and lock one exact proposal/SOW revision" — this modifies the state of a document by locking it, which is a reversible state change.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs approve_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 approve_consulting_document_revision, this is the rule to start with:

approve_consulting_document_revision Rate-limited

approve_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "approve_consulting_document_revision": {
      "limits": [
        {
          "counter": "approve_consulting_document_revision_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every approve_consulting_document_revision call is checked against it from then on.

FAQ

Questions about approve_consulting_document_revision

What does the approve_consulting_document_revision tool do? +

Approve and lock one exact proposal/SOW revision. Requires the separate consulting:approve scope and never publishes or shares it. 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.

What parameters does approve_consulting_document_revision accept? +

approve_consulting_document_revision accepts 3 parameters: document_id, expected_version, expected_content_hash. Required: document_id, expected_version, expected_content_hash. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on approve_consulting_document_revision? +

Register the Meta Council MCP server in PolicyLayer and add a rule for approve_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.

What risk level is approve_consulting_document_revision? +

approve_consulting_document_revision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit approve_consulting_document_revision? +

Yes. Add a rate_limit block to the approve_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.

How do I block approve_consulting_document_revision completely? +

Set action: deny in the PolicyLayer policy for approve_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.

What MCP server provides approve_consulting_document_revision? +

approve_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.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →