Initializes asset upload and returns signed S3 upload URL
AI agents use init-asset-upload 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 creates new assets in Storyblok by initiating an upload process and providing credentials (signed S3 URL) for asset creation. While it doesn't directly delete or destroy data, and doesn't move money, it does create/add new content to the CMS.
From the tool's definition Tool initializes asset upload and returns signed S3 URL, enabling creation of new assets in the CMS. The description explicitly states 'upload' functionality, which is a write operation that creates new data in the system.
Attacks that exploit this kind of access
Initializes asset upload and returns signed S3 upload URL. 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 init-asset-upload: 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.
init-asset-upload 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 init-asset-upload 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 init-asset-upload. 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.
init-asset-upload 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 →