Move multiple assets to a specified folder.
AI agents use bulk_move_assets to create or update resources in Storyblok MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Storyblok MCP Server environment.
Moving assets to different folders modifies their organizational state/metadata but does not delete, destroy, or irreversibly alter the asset data itself. This is a reversible write operation. Severity is medium because bulk operations affecting multiple assets could cause organizational confusion if misapplied, but the action remains undoable through moving assets back to their original location.
From the tool's definition Tool name 'bulk_move_assets' and description 'Move multiple assets to a specified folder' indicate modification of asset metadata/organization without deletion or creation of new assets.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access bulk_move_assets gives an agent:
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 bulk_move_assets:
{
"version": "1",
"default": "deny",
"tools": {
"bulk_move_assets": {
"limits": [
{
"counter": "bulk_move_assets_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bulk_move_assets 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.
Free to start. No card required.
Move multiple assets to a specified folder. It is categorised as a Write tool in the Storyblok MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for bulk_move_assets: 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.
bulk_move_assets 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 bulk_move_assets 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 bulk_move_assets. 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.
bulk_move_assets 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.
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.