create_blog_category
Create a blog/article category. Returns the new category id — pass it to create_article
This record as markdown: /tools/webcake-storefront/create-blog-category.md
What create_blog_category does on Webcake Storefront
AI agents use create_blog_category to create or update resources in Webcake Storefront, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Webcake Storefront environment.
Why create_blog_category is rated Medium
Creating a blog category is a write operation that creates new data structures reversibly—the category can be modified or deleted later. This is less severe than Execute (no arbitrary code) or Destructive (creation is undoable), and not a Read operation since it modifies state.
From the tool's definition Tool description states "Create a blog/article category" which indicates a data creation operation that generates a new category resource with an id. This is a reversible write operation typical of content management systems.
Attacks that exploit this kind of access
The rule that runs create_blog_category safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_blog_category, this is the rule to start with:
create_blog_category 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 Webcake Storefront, apply this rule, and every create_blog_category call is checked against it from then on.
Questions about create_blog_category
Create a blog/article category. Returns the new category id — pass it to create_article. It is categorised as a Write tool in the Webcake Storefront MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Webcake Storefront MCP server in PolicyLayer and add a rule for create_blog_category: 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 Webcake Storefront. Nothing to install.
create_blog_category 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 create_blog_category 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 create_blog_category. 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.
create_blog_category is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Webcake Storefront, and thousands of servers like it.
This server
Across the catalogue