update_content_asset
Edit an owned draft. Submitted/approved/rejected revisions are immutable and must be revised.
This record as markdown: /tools/com-meta-council-decision-intelligence/update-content-asset.md
What update_content_asset does on Meta Council
AI agents use update_content_asset 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 update_content_asset is rated Medium
This tool creates or modifies data in a reversible manner—it edits draft content assets but explicitly preserves immutability for submitted/approved/rejected states, preventing destructive overwrites. The ability to edit drafts qualifies as Write category.
From the tool's definition Tool description states 'Edit an owned draft', which is a direct modification operation. The clarification that 'Submitted/approved/rejected revisions are immutable' indicates this tool modifies reversible draft states only.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs update_content_asset 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_content_asset, this is the rule to start with:
update_content_asset 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_content_asset call is checked against it from then on.
Questions about update_content_asset
Edit an owned draft. Submitted/approved/rejected revisions are immutable and must be revised. 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_content_asset 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 update_content_asset: 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_content_asset 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_content_asset 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_content_asset. 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_content_asset 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