get_checkout_page
Get a checkout page with its public URL and sales analytics.
This record as markdown: /tools/app-businys-mcp-server/get-checkout-page.md
What get_checkout_page does on Businys
AI agents call get_checkout_page to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_checkout_page is rated Low
This tool retrieves checkout page information and associated analytics. It queries or fetches data without creating, modifying, deleting, or executing external operations. The action is informational and read-only, making it a Read category tool with low severity since unauthorized access would only expose data but not compromise business operations or financial transactions.
From the tool's definition The description states 'Get a checkout page with its public URL and sales analytics.' The verb 'Get' and the retrieval of existing data (checkout page details, URL, analytics) indicate a read-only operation with no modifications to data.
Attacks that exploit this kind of access
The rule that runs get_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 get_checkout_page, this is the rule to start with:
get_checkout_page is read-only, so it stays allowed. 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 get_checkout_page call is checked against it from then on.
Questions about get_checkout_page
Get a checkout page with its public URL and sales analytics. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for get_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.
get_checkout_page is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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