// SCAN REPORT

MCP Storyblok Server

48 tools. 26 can modify or destroy data without limits.

7 destructive tools with no built-in limits. Policy required.

Last updated:

26 can modify or destroy data
22 read-only
48 tools total

Community server · catalogue entry verified 01/07/2026

How to control MCP Storyblok Server ↓

TOOL MAP

What MCP Storyblok Server exposes to your agents

Read (22) Write / Execute (19) Destructive / Financial (7)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS
Critical Risk

The most dangerous MCP Storyblok Server tools

Destructive · High bulk-delete-stories This tool permanently removes stories from the CMS without possibility of reversal. Destructive · High delete-asset Deletion of assets is an irreversible operation that cannot be undone. Destructive · High delete-asset-folder This tool permanently removes an asset folder and its contents from the Storyblok CMS without the ability to undo the action. Destructive · High delete-component Deleting a component from a CMS is a destructive operation that cannot be undone.

26 of MCP Storyblok Server's 48 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MCP Storyblok Server

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Storyblok Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "bulk-delete-stories": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "add-story-to-release": {
    "limits": [
      {
        "counter": "add-story-to-release_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "debug-story-access": {
    "limits": [
      {
        "counter": "debug-story-access_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register MCP Storyblok Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON MCP STORYBLOK →

Instant setup, no code required.

FULL CATALOGUE

All 48 MCP Storyblok Server tools

DESTRUCTIVE 7 tools
Destructive bulk-delete-stories Deletes multiple stories in Storyblok Destructive delete-asset Deletes an asset from Storyblok Destructive delete-asset-folder Deletes an asset folder from Storyblok Destructive delete-component Deletes a component from Storyblok Destructive delete-release Deletes a release Destructive delete-story Deletes a story from Storyblok Destructive delete-tag Deletes a tag from Storyblok
WRITE 19 tools
Write add-story-to-release Adds a story to an existing release Write bulk-create-stories Creates multiple stories in Storyblok Write bulk-publish-stories Publishes multiple stories in Storyblok Write bulk-update-stories Updates multiple stories in Storyblok Write complete-asset-upload Completes the asset upload process after S3 upload Write create-asset-folder Creates a new asset folder in Storyblok Write create-component Creates a new component (block) in Storyblok Write create-release Creates a new release in Storyblok Write create-story Creates a new story in Storyblok Write create-tag Creates a new tag in Storyblok Write create-tag-and-add-to-story Create a new tag in your Storyblok space and add it to a story Write init-asset-upload Initializes asset upload and returns signed S3 upload URL Write publish-release Publishes a release Write publish-story Publishes a story in Storyblok Write restore-story Restores a story to a specific version Write unpublish-story Unpublishes a story in Storyblok Write update-asset-folder Updates an existing asset folder in Storyblok Write update-component Updates an existing component in Storyblok Write update-story Updates an existing story in Storyblok
READ 22 tools
Read debug-story-access Debugs access to a specific story by trying various fetch parameters. Read fetch-asset-folders Fetches asset folders from Storyblok space Read fetch-assets Fetches assets from Storyblok space with optional filtering Read fetch-components Fetches components from Storyblok space, with optional filtering and response shaping. Read fetch-datasources Fetches datasources from Storyblok space Read fetch-folders Fetches folders from Storyblok space Read fetch-releases Fetches all releases from Storyblok space Read fetch-stories Fetches stories from Storyblok space with optional filtering Read fetch-stories-by-component Fetches stories from Storyblok space filtering by a specific component name in story content or body. Read fetch-tags Fetches all tags from Storyblok space Read get-asset Gets a specific asset by ID Read get-component Gets a specific component by ID Read get-component-usage Finds all stories where a specific component is used, checking direct use and nested use within the story cont Read get-space Gets information about the current Storyblok space Read get-story Gets a specific story by ID or slug Read get-story-by-slug Gets a story by its slug using the Content Delivery API Read get-story-versions Gets all versions of a story Read list_tools Lists all available tools with their names and descriptions. Read ping Checks server health and Storyblok API connectivity. Read search-content Searches for a query string within specified fields of story content, with options for content type filtering Read search-stories Search stories using the Content Delivery API with advanced filtering Read validate-story-content Validates a story
EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Yaver 1060 tools
admin
Nodebench 824 tools
admin
UnClick 813 tools
admin
Binance MCP Server 734 tools
admin
Pfsense 680 tools
admin
AdButler 622 tools
admin
Fortimanager 584 tools
admin
Crow 573 tools
admin
FAQ

Questions about MCP Storyblok Server

Can an AI agent delete data through the MCP Storyblok Server MCP server? +

Yes. The MCP Storyblok Server server exposes 7 destructive tools including bulk-delete-stories, delete-asset, delete-asset-folder. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through MCP Storyblok Server? +

The MCP Storyblok Server server has 19 write tools including add-story-to-release, bulk-create-stories, bulk-publish-stories. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach MCP Storyblok Server.

How many tools does the MCP Storyblok Server MCP server expose? +

48 tools across 3 categories: Destructive, Read, Write. 22 are read-only. 26 can modify, create, or delete data.

How do I enforce a policy on MCP Storyblok Server? +

Register the MCP Storyblok Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MCP Storyblok Server tool call.

Deterministic rules across all 48 MCP Storyblok Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP STORYBLOK →

Instant setup, no code required.

48 MCP Storyblok Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.