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.
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.
Documented attack patterns abuse exactly the kind of access import_story 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 import_story:
{
"version": "1",
"default": "deny",
"tools": {
"import_story": {
"limits": [
{
"counter": "import_story_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_story 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.
import_story. 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 import_story: 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.
import_story 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 import_story 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 import_story. 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.
import_story is provided by the Storyblok MCP Server MCP server (arjuncodess/storyblok-mcp). 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.
115 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.