AI agents use register_creative_asset to create or update resources in Raven — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Raven environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
uri | string | Yes | Local path or URL to the asset. |
name | string | — | Human-readable name. |
tags | array | — | Search tags. |
type | string | Yes | Asset type. |
metadata | object | — | Optional non-secret metadata. |
description | string | — | What this asset should be used for. |
Parameters from the server's own tool schema.
This tool creates new records (asset registrations with metadata and references) in the Raven system. It is reversible (assets can be unregistered or re-registered) and does not delete data, execute arbitrary code, or move money.
From the tool's definition Tool description states it 'Register[s] a local or remote creative asset for Raven jobs' and 'Raven stores metadata and a URI/path'. The verb 'register' combined with storage of metadata indicates data creation/modification without deletion.
Risk signalsAccepts URL/endpoint input (uri)
Attacks that exploit this kind of access
Register a local or remote creative asset for Raven jobs. This is the local-first analog of upload: Raven stores metadata and a URI/path, not the file bytes. It is categorised as a Write tool in the Raven MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
register_creative_asset accepts 6 parameters: uri, name, tags, type, metadata, description. Required: uri, type. The full parameter table on this page comes from the server's own tool schema.
Register the Raven MCP server in PolicyLayer and add a rule for register_creative_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 Raven. Nothing to install.
register_creative_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 register_creative_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 register_creative_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.
register_creative_asset is provided by the Raven MCP server (raven-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →