get_content_asset
Get one owned content revision, including its review state and exact content hashes.
This record as markdown: /tools/com-meta-council-decision-intelligence/get-content-asset.md
What get_content_asset does on Meta Council
AI agents call get_content_asset 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 |
|---|---|---|---|
asset_id | string | Yes | Full UUID from the matching list tool. |
Parameters from the server's own tool schema.
Why get_content_asset is rated Low
This tool retrieves and queries data about a content asset without creating, modifying, or deleting anything. It is a read-only operation that returns existing information about owned content revisions.
From the tool's definition Tool name 'get_content_asset' and description 'Get one owned content revision' indicate a retrieval operation with no side effects. The description specifies reading metadata (review state, content hashes) only.
Attacks that exploit this kind of access
The rule that runs get_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 get_content_asset, this is the rule to start with:
get_content_asset is read-only, so it stays allowed. 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 get_content_asset call is checked against it from then on.
Questions about get_content_asset
Get one owned content revision, including its review state and exact content hashes. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_content_asset accepts 1 parameter: 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 get_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.
get_content_asset is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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