update-component · MCP Storyblok Server MCP: Risk & Policy

WHAT IT DOES

What update-component does on MCP Storyblok Server

AI agents use update-component 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.

WHY IT NEEDS A POLICY

Why update-component needs a policy

This tool creates or modifies data reversibly, fitting the Write category. Severity is medium because updating components in a CMS could affect published content and user-facing systems if done incorrectly, but the blast radius is limited to component definitions rather than arbitrary code execution or data destruction. The confidence is high given the explicit 'update' action and CMS context.

From the tool's definition Tool name 'update-component' and description 'Updates an existing component in Storyblok' indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-component Rate-limited

update-component 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update-component": {
      "limits": [
        {
          "counter": "update-component_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Storyblok Server, so you can run agents against it safely.

FAQ

Questions about update-component

What does the update-component tool do? +

Updates an existing component in Storyblok. 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.

How do I enforce a policy on update-component? +

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

What risk level is update-component? +

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

Can I rate-limit update-component? +

Yes. Add a rate_limit block to the update-component 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 completely? +

Set action: deny in the PolicyLayer policy for update-component. 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? +

update-component 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.