Low Risk

fetch_asset_folder

Fetch details of a specific asset folder by its ID.

How to control fetch_asset_folder ↓

What fetch_asset_folder does on Storyblok MCP Server

AI agents call fetch_asset_folder to retrieve information from Storyblok MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why fetch_asset_folder needs a policy

This tool retrieves metadata about an asset folder without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk even if misused by an AI agent, as it only returns existing folder information.

From the tool's definition Tool name 'fetch_asset_folder' and description 'Fetch details of a specific asset folder by its ID' indicate a retrieval operation with no modification or deletion. The verb 'fetch' and the focus on 'details' confirm this is a read-only query.

Documented attack patterns abuse exactly the kind of access fetch_asset_folder gives an agent:

How to control fetch_asset_folder

PolicyLayer is an MCP gateway — it sits between your AI agents and Storyblok MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_asset_folder:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_asset_folder": {}
  }
}

fetch_asset_folder is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Storyblok MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fetch_asset_folder

What does the fetch_asset_folder tool do? +

Fetch details of a specific asset folder by its ID. It is categorised as a Read tool in the Storyblok MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_asset_folder? +

Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for fetch_asset_folder: 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 Storyblok MCP Server. Nothing to install.

What risk level is fetch_asset_folder? +

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

Can I rate-limit fetch_asset_folder? +

Yes. Add a rate_limit block to the fetch_asset_folder 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_folder completely? +

Set action: deny in the PolicyLayer policy for fetch_asset_folder. 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_folder? +

fetch_asset_folder is provided by the Storyblok MCP Server MCP server (kiran1689/storyblok-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Storyblok MCP Server tool call.

Start from Storyblok MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

159 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.