ecommerce_payment_manual
Enable manual payment method for a store.
This record as markdown: /tools/hostinger-mcp/ecommerce-payment-manual.md
What ecommerce_payment_manual does on Hostinger
AI agents use ecommerce_payment_manual to commit financial operations through Hostinger, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why ecommerce_payment_manual is rated Critical
This tool modifies payment configuration for an e-commerce store by enabling a manual payment method. Changes to payment methods directly affect financial transaction flows — enabling or disabling how customers can pay. This falls under the Financial category as it commits changes to financial infrastructure. Misuse could allow unauthorized payment methods, redirect payments, or disrupt checkout flows.
From the tool's definition Enable manual payment method for a store
Attacks that exploit this kind of access
The rule that runs ecommerce_payment_manual safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ecommerce_payment_manual, this is the rule to start with:
Any call to ecommerce_payment_manual is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every ecommerce_payment_manual call is checked against it from then on.
Questions about ecommerce_payment_manual
Enable manual payment method for a store. It is categorised as a Financial tool in the Hostinger MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Hostinger MCP server in PolicyLayer and add a rule for ecommerce_payment_manual: 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 Hostinger. Nothing to install.
ecommerce_payment_manual is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ecommerce_payment_manual 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 ecommerce_payment_manual. 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.
ecommerce_payment_manual is provided by the Hostinger MCP server (idugeni/hostinger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger, and thousands of servers like it.
Across the catalogue