update_course
Update a course by id (partial). Pass
This record as markdown: /tools/webcake-storefront/update-course.md
What update_course does on Webcake Storefront
AI agents use update_course 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 update_course is rated Medium
This tool creates or modifies data reversibly without deleting it, fitting the Write category. Severity is high because unintended course updates in an e-commerce storefront could disrupt customer experience, product listings, or service delivery. The incomplete description ('Pass' cuts off) lowers confidence slightly, but the intent is clear from the name and context (storefront with products/orders/authoring).
From the tool's definition Tool name 'update_course' and description 'Update a course by id (partial)' indicate modification of existing data. The word 'Update' and 'partial' suggest reversible changes to course records in a storefront system.
Attacks that exploit this kind of access
The rule that runs update_course 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 update_course, this is the rule to start with:
update_course 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 update_course call is checked against it from then on.
Questions about update_course
Update a course by id (partial). Pass. 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 update_course: 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.
update_course 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 update_course 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 update_course. 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.
update_course 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