AI agents use create_component_folder 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.
This tool creates new data (a folder structure) within Storyblok, making it a Write-category operation. It is reversible—folders can be deleted. The severity is medium because misconfiguration or abuse could create numerous unwanted folders, cluttering the component organization and potentially causing operational confusion, but the impact is contained and can be undone.
From the tool's definition Tool creates a new component folder in the Storyblok space, which is a write operation that creates data structure reversibly. The description explicitly states 'Creates a new component folder.'
Documented attack patterns abuse exactly the kind of access create_component_folder 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 create_component_folder:
{
"version": "1",
"default": "deny",
"tools": {
"create_component_folder": {
"limits": [
{
"counter": "create_component_folder_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_component_folder 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.
Creates a new component 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 create_component_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.
create_component_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 create_component_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 create_component_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.
create_component_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.
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.