update_checkout_page
Update a checkout page (title, price, description, active status).
This record as markdown: /tools/app-businys-mcp-server/update-checkout-page.md
What update_checkout_page does on Businys
AI agents use update_checkout_page to create or update resources in Businys, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Businys environment.
Why update_checkout_page is rated Medium
This tool modifies checkout page configuration including pricing and activation status, which directly impacts customer transactions and revenue. While reversible (Write rather than Destructive), the ability to alter prices and active status creates high risk if misused by an agent—prices could be set to zero, pages disabled, or customers charged incorrectly. The financial implications elevate severity beyond medium.
From the tool's definition Tool name 'update_checkout_page' and description explicitly states it modifies checkout page properties including 'price' and 'active status', indicating reversible creation/modification of e-commerce data.
Attacks that exploit this kind of access
The rule that runs update_checkout_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_checkout_page, this is the rule to start with:
update_checkout_page 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 Businys, apply this rule, and every update_checkout_page call is checked against it from then on.
Questions about update_checkout_page
Update a checkout page (title, price, description, active status). It is categorised as a Write tool in the Businys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Businys MCP server in PolicyLayer and add a rule for update_checkout_page: 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 Businys. Nothing to install.
update_checkout_page 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_checkout_page 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_checkout_page. 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_checkout_page is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue