New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

ecommerce_payment_manual

Enable manual payment method for a store.

SERVERHostinger SOURCEidugeni/hostinger-mcp
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about ecommerce_payment_manual

What does the ecommerce_payment_manual tool do? +

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.

How do I enforce a policy on ecommerce_payment_manual? +

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.

What risk level is ecommerce_payment_manual? +

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.

Can I rate-limit ecommerce_payment_manual? +

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.

How do I block ecommerce_payment_manual completely? +

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.

What MCP server provides ecommerce_payment_manual? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hostinger's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.