Completes the asset upload process after S3 upload
AI agents use complete-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 finalizes an asset upload, which creates or registers new assets in Storyblok. This is a Write operation because it modifies the CMS state by adding/storing asset metadata. It is not Destructive (no deletion), Execute (not arbitrary code), or Financial.
From the tool's definition Tool name 'complete-asset-upload' and description 'Completes the asset upload process after S3 upload' indicate file finalization that creates or registers an asset in the CMS.
Attacks that exploit this kind of access
Completes the asset upload process after S3 upload. 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 complete-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.
complete-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 complete-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 complete-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.
complete-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 →