create_content_asset_revision
Create a new owned draft revision from a frozen submitted/approved/rejected revision.
This record as markdown: /tools/com-meta-council-decision-intelligence/create-content-asset-revision.md
What create_content_asset_revision does on Meta Council
AI agents use create_content_asset_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 |
|---|---|---|---|
title | string | — | |
channel | string | — | |
content | string | — | |
asset_id | string | Yes | Full UUID from the matching list tool. |
asset_type | string | — | |
scheduled_for | string | — | |
revision_notes | string | — |
Parameters from the server's own tool schema.
Why create_content_asset_revision is rated Medium
This tool creates and modifies content assets by generating new revisions, which is a write operation. It does not delete data irreversibly (thus not Destructive), does not execute arbitrary code (thus not Execute), and does not transfer funds (thus not Financial).
From the tool's definition Tool description states it 'Create[s] a new...revision' from an existing revision, indicating content creation and modification. The tool operates on content assets and produces a new draft state, which is reversible.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs create_content_asset_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_content_asset_revision, this is the rule to start with:
create_content_asset_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_content_asset_revision call is checked against it from then on.
Questions about create_content_asset_revision
Create a new owned draft revision from a frozen submitted/approved/rejected revision. 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_content_asset_revision accepts 7 parameters: title, channel, content, asset_id, asset_type, scheduled_for, revision_notes. Required: asset_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_content_asset_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_content_asset_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_content_asset_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_content_asset_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_content_asset_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