import_story

What import_story does on Storyblok MCP Server

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

Why import_story is rated Medium

Importing a story into a CMS creates or adds new content records, which is a reversible write operation. It modifies the state of the content management system by introducing new data, but the operation can typically be undone by deleting or reverting the imported story. This is less severe than destructive operations (which cannot be easily undone) and does not execute arbitrary code or move money.

From the tool's definition Tool name is 'import_story' which indicates creating or adding story content to the CMS. Sibling tools like 'add_story_to_release', 'copy_stories_between_branches', and 'backup_space' confirm this server manages content creation and modification.

The rule that runs import_story safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Storyblok MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_story, this is the rule to start with:

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

Questions about import_story