update_component_folder

THE RISK

Medium Risk

Why update_component_folder needs a policy

This tool modifies component organization metadata reversibly without deleting data or executing arbitrary code. While it affects a foundational content structure used across stories, the change is non-destructive and can be reverted through another update.

From the tool's definition Tool name 'update_component_folder' explicitly indicates modification ('update') of an existing component folder structure. Description states it 'Updates an existing component folder (component group)', confirming write operation on content metadata.

Documented attack patterns abuse exactly the kind of access update_component_folder gives an agent:

POLICY

How to control update_component_folder

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 update_component_folder:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_component_folder": {
      "limits": [
        {
          "counter": "update_component_folder_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_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.

Create a free account and register Storyblok MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Storyblok MCP Server tools

Destructive bulk_delete_stories Deletes multiple stories in Storyblok. Destructive delete_access_token Delete an access token from the current Storyblok space using the Management API. Destructive delete_approval Deletes an approval from a specified Storyblok space. Destructive delete_asset Deletes an asset from Storyblok. Destructive delete_asset_folder Delete an asset folder from the current Storyblok space. Destructive delete_branch Deletes a branch (pipeline) by its ID in a Storyblok space. Destructive delete_collaborator Deletes a collaborator from a specified Storyblok space. Destructive delete_comment Deletes a comment from a discussion via the Storyblok Management API.

All 159 Storyblok MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_component_folder

What does the update_component_folder tool do? +

Updates an existing component folder (component group). 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.

How do I enforce a policy on update_component_folder? +

Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_component_folder? +

update_component_folder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_component_folder? +

Yes. Add a rate_limit block to the update_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.

How do I block update_component_folder completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_component_folder? +

update_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.

Enforce policy on every Storyblok MCP Server tool call.

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.

CHECK YOUR STACK →