approve_content_asset
Approve a submitted owned revision and attest to its exact content hash. Requires marketing:approve, separate from draft authority.
This record as markdown: /tools/com-meta-council-decision-intelligence/approve-content-asset.md
What approve_content_asset does on Meta Council
AI agents use approve_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 |
|---|---|---|---|
notes | string | — | |
asset_id | string | Yes | Full UUID from the matching list tool. |
Parameters from the server's own tool schema.
Why approve_content_asset is rated Medium
This tool creates or modifies a reversible record (an approval attestation on a content asset revision). It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely read data (not Read). The Write category applies because approval operations typically create audit records and change workflow states.
From the tool's definition Tool description states "Approve a submitted owned revision" — this modifies the status/state of a content asset by attestation, making it an approval action that changes data state.
Attacks that exploit this kind of access
The rule that runs approve_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 approve_content_asset, this is the rule to start with:
approve_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 approve_content_asset call is checked against it from then on.
Questions about approve_content_asset
Approve a submitted owned revision and attest to its exact content hash. Requires marketing:approve, separate from draft authority. 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.
approve_content_asset accepts 2 parameters: notes, asset_id. 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 approve_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.
approve_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 approve_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 approve_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.
approve_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