auto_tag_story

A write tool on the Storyblok MCP server.

SERVERStoryblok MCP Server SOURCEarjuncodess/storyblok-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arjuncodess-storyblok-mcp/auto-tag-story.md

WHAT IT DOES

What auto_tag_story does on Storyblok MCP Server

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

RISK

Why auto_tag_story is rated Medium

The tool name suggests it automatically applies tags to a story (content item) in Storyblok CMS, which is a write/modify operation. However, the description is empty, so confidence is low. Based on the naming convention and the server's purpose of content management, this likely modifies metadata on existing stories by adding tags.

From the tool's definition Tool name 'auto_tag_story' and server context managing Storyblok CMS content

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs auto_tag_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 auto_tag_story, this is the rule to start with:

auto_tag_story Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every auto_tag_story call is checked against it from then on.

FAQ

Questions about auto_tag_story

What does the auto_tag_story tool do? +

auto_tag_story is a write tool on the Storyblok MCP Server MCP server. 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 auto_tag_story? +

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

What risk level is auto_tag_story? +

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

Can I rate-limit auto_tag_story? +

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

How do I block auto_tag_story completely? +

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

What MCP server provides auto_tag_story? +

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

KEEP EXPLORING

More on Storyblok MCP Server, and thousands of servers like it.

This server

All 115 Storyblok MCP Server tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_tag on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →