list_content_assets

List owned content assets and immutable revisions; content is never published by this tool.

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/list-content-assets.md

WHAT IT DOES

What list_content_assets does on Meta Council

AI agents call list_content_assets 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
`limit`	integer	—
`campaign_id`	string	—	Full UUID from the matching list tool.
`approval_state`	string	—
`include_archived`	boolean	—

Parameters from the server's own tool schema.

RISK

Why list_content_assets is rated Low

This tool retrieves and lists existing content assets and their revisions. It performs a read-only query operation with no ability to create, modify, delete, or publish data. The explicit statement that content is never published further confirms this is a passive data retrieval function with minimal risk.

From the tool's definition Tool description explicitly states 'List owned content assets' which is a retrieval/query operation, and clarifies 'content is never published by this tool', confirming no side effects or modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_content_assets 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 list_content_assets, this is the rule to start with:

list_content_assets Allowed

list_content_assets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_content_assets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every list_content_assets call is checked against it from then on.

FAQ

Questions about list_content_assets

What does the list_content_assets tool do? +

List owned content assets and immutable revisions; content is never published by this tool. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

What parameters does list_content_assets accept? +

list_content_assets accepts 4 parameters: limit, campaign_id, approval_state, include_archived. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_content_assets? +

Register the Meta Council MCP server in PolicyLayer and add a rule for list_content_assets: 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.

What risk level is list_content_assets? +

list_content_assets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_content_assets? +

Yes. Add a rate_limit block to the list_content_assets 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.

How do I block list_content_assets completely? +

Set action: deny in the PolicyLayer policy for list_content_assets. 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.

What MCP server provides list_content_assets? +

list_content_assets 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.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →