update_asset
Updates the name and/or description of an existing asset. The URL does not change. At least one of name or description must be provided. Requires authentication with at least content_only scope.
This record as markdown: /tools/de-agentview-agentview-mcp/update-asset.md
What update_asset does on agentView
AI agents use update_asset to create or update resources in agentView, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your agentView environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | New filename for the asset. |
asset_id | string | Yes | The asset ID to update. |
description | string | — | New description for the asset. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why update_asset is rated Medium
This tool creates or modifies data (asset metadata) in a reversible manner without deleting or overwriting irreversibly. It falls squarely into the Write category. Severity is medium because an AI agent could modify asset metadata across displays in unintended ways, but the impact is limited to asset naming/descriptions rather than content delivery or financial operations.
From the tool's definition Tool description states 'Updates the name and/or description of an existing asset', which is a modification operation. The tool requires authentication and has scope constraints ('content_only'), indicating it modifies data reversibly.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs update_asset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_asset, this is the rule to start with:
update_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 agentView, apply this rule, and every update_asset call is checked against it from then on.
Questions about update_asset
Updates the name and/or description of an existing asset. The URL does not change. At least one of name or description must be provided. Requires authentication with at least content_only scope. It is categorised as a Write tool in the agentView MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_asset accepts 4 parameters: name, asset_id, description, access_token. Required: asset_id. The full parameter table on this page comes from the server's own tool schema.
Register the agentView MCP server in PolicyLayer and add a rule for update_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 agentView. Nothing to install.
update_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 update_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 update_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.
update_asset is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on agentView, and thousands of servers like it.
This server
Across the catalogue