reject_content_asset
Reject a submitted owned revision with optional reviewer notes. Requires marketing:approve.
This record as markdown: /tools/com-meta-council-decision-intelligence/reject-content-asset.md
What reject_content_asset does on Meta Council
AI agents use reject_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 reject_content_asset is rated Medium
This tool changes data (content asset status) reversibly rather than deleting it. The asset and its revision remain in the system; only its approval state changes. This is a Write operation (status modification), not Read (no querying), not Destructive (not permanent deletion), not Execute (no arbitrary code/commands), not Financial.
From the tool's definition Tool description states 'Reject a submitted owned revision' - this modifies the state of a content asset by changing its status from submitted to rejected, a reversible action.
Attacks that exploit this kind of access
The rule that runs reject_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 reject_content_asset, this is the rule to start with:
reject_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 reject_content_asset call is checked against it from then on.
Questions about reject_content_asset
Reject a submitted owned revision with optional reviewer notes. Requires marketing:approve. 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.
reject_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 reject_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.
reject_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 reject_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 reject_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.
reject_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