get_asset
Returns metadata for a single asset including its URL. Use this to verify an asset still exists before referencing it in HTML. Requires authentication with at least content_only scope.
This record as markdown: /tools/de-agentview-agentview-mcp/get-asset.md
What get_asset does on agentView
AI agents call get_asset to retrieve information from agentView 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 | The asset ID (e.g. 'ast_01H7KXZ...'). |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why get_asset is rated Low
This tool retrieves metadata about an asset without creating, modifying, deleting, or executing anything. It is explicitly a verification/query operation (confirming an asset exists before reference). The requirement for authentication with 'content_only' scope further indicates this is a read-only operation with minimal privilege. No side effects or irreversible actions are possible.
From the tool's definition Tool name is 'get_asset' and description states it 'Returns metadata for a single asset including its URL' — a retrieval operation with no modification, deletion, or execution.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs get_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 get_asset, this is the rule to start with:
get_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 agentView, apply this rule, and every get_asset call is checked against it from then on.
Questions about get_asset
Returns metadata for a single asset including its URL. Use this to verify an asset still exists before referencing it in HTML. Requires authentication with at least content_only scope. It is categorised as a Read tool in the agentView MCP Server, which means it retrieves data without modifying state.
get_asset accepts 2 parameters: asset_id, 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 get_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.
get_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_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_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_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