Updates an existing asset folder in Storyblok
AI agents use update-asset-folder to create or update resources in MCP Storyblok Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Storyblok Server environment.
This tool modifies asset folder attributes in the CMS, which is a reversible change. While it affects content organization, the operation can be undone by reverting changes. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or involve financial operations.
From the tool's definition Tool name and description: 'Updates an existing asset folder in Storyblok' — modifies existing data structure (folder properties, metadata, naming, organization) reversibly without deletion or permanent data loss.
Attacks that exploit this kind of access
Updates an existing asset folder in Storyblok. It is categorised as a Write tool in the MCP Storyblok Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Storyblok Server MCP server in PolicyLayer and add a rule for update-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 MCP Storyblok Server. Nothing to install.
update-asset-folder 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-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.
Set action: deny in the PolicyLayer policy for update-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.
update-asset-folder is provided by the MCP Storyblok Server MCP server (zerdos/mcp-storyblok-server). 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 →