project_document_revise
Append an immutable document revision using expected_revision and a caller-retained request_id. Exact retry reconciles even after later edits; changed input or stale base conflicts. No provider execution or external publication.
This record as markdown: /tools/com-meta-council-decision-intelligence/project-document-revise.md
What project_document_revise does on Meta Council
AI agents call project_document_revise to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | |
kind | string | Yes | |
title | string | Yes | |
status | string | — | |
ticket_id | object | — | |
project_id | string | Yes | |
request_id | string | Yes | |
document_id | string | Yes | |
expected_revision | integer | Yes |
Parameters from the server's own tool schema.
Why project_document_revise is rated Low
Even though project_document_revise only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs project_document_revise 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 project_document_revise, this is the rule to start with:
project_document_revise is read-only, so it stays allowed. 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 project_document_revise call is checked against it from then on.
Questions about project_document_revise
Append an immutable document revision using expected_revision and a caller-retained request_id. Exact retry reconciles even after later edits; changed input or stale base conflicts. No provider execution or external publication. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
project_document_revise accepts 9 parameters: body, kind, title, status, ticket_id, project_id, request_id, document_id, expected_revision. Required: body, kind, title, project_id, request_id, document_id, expected_revision. 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 project_document_revise: 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.
project_document_revise is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the project_document_revise 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 project_document_revise. 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.
project_document_revise 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