generate_meta
A write tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/generate-meta.md
What generate_meta does on Storyblok MCP Server
AI agents use generate_meta 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 generate_meta is rated Medium
Without a description, we infer purpose from context: on a CMS platform, 'generate_meta' most likely creates or updates metadata (e.g., SEO meta tags, descriptions) associated with content. This is a reversible modification operation, matching Write category. Severity is medium because metadata changes can affect content presentation or SEO but are typically undoable.
From the tool's definition Tool name 'generate_meta' on a CMS (Storyblok) server suggests metadata generation; sibling tools include 'create_access_token', 'create_branch', and other write operations that create or modify content.
Attacks that exploit this kind of access
The rule that runs generate_meta 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 generate_meta, this is the rule to start with:
generate_meta 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every generate_meta call is checked against it from then on.
Questions about generate_meta
generate_meta 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.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for generate_meta: 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.
generate_meta 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 generate_meta 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 generate_meta. 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.
generate_meta 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.
More on Storyblok MCP Server, and thousands of servers like it.
This server
Across the catalogue