fetch_asset

Resolve a generated asset reference (a /generated/… path or any URL) to a clickable absolute URL + a direct download URL.

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/fetch-asset.md

WHAT IT DOES

What fetch_asset does on Hermoso

AI agents call fetch_asset to retrieve information from Hermoso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why fetch_asset is rated Low

This tool retrieves metadata about previously generated assets and returns URLs for access or download. It has no capability to modify, delete, execute code, move money, or trigger external operations. It is a straightforward lookup/retrieval utility with minimal security risk.

From the tool's definition Tool description states it 'Resolve[s] a generated asset reference... to a clickable absolute URL + a direct download URL.' The verbs 'resolve' and the action of returning URLs are read-only retrieval operations with no data modification or execution side…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fetch_asset safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch_asset, this is the rule to start with:

fetch_asset Allowed

fetch_asset 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": {
    "fetch_asset": {}
  }
}

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

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

FAQ

Questions about fetch_asset

What does the fetch_asset tool do? +

Resolve a generated asset reference (a /generated/… path or any URL) to a clickable absolute URL + a direct download URL. It is categorised as a Read tool in the Hermoso MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_asset? +

Register the Hermoso MCP server in PolicyLayer and add a rule for fetch_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 Hermoso. Nothing to install.

What risk level is fetch_asset? +

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

Can I rate-limit fetch_asset? +

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

How do I block fetch_asset completely? +

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

What MCP server provides fetch_asset? +

fetch_asset is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hermoso, and thousands of servers like it.

This server

All 896 Hermoso tools →

Across the catalogue

The MCP Attack Database →

Guides

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