ecommerce_enableManualPaymentMethodV1

Enable a manual payment method so the store can accept orders without an online payment provider.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/ecommerce-enablemanualpaymentmethodv1.md

WHAT IT DOES

What ecommerce_enableManualPaymentMethodV1 does on Hostinger Api

AI agents use ecommerce_enableManualPaymentMethodV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

Parameter	Type	Required	Description
`title`	string	—	Optional display name shown to customers at checkout.
`store_id`	string	Yes	The ID of the store to enable manual payment for.

Parameters from the server's own tool schema.

RISK

Why ecommerce_enableManualPaymentMethodV1 is rated Medium

This tool creates or modifies the store's payment configuration by enabling a manual payment method. It is reversible (can be disabled), so it falls under Write rather than Destructive. However, the severity is high because enabling alternative payment methods could be abused to redirect financial transactions, accept fraudulent orders, or disrupt normal payment processing.

From the tool's definition Tool name contains 'enable' and description states it allows the store to 'accept orders' by enabling a payment method. This modifies the store's configuration to accept a new payment mechanism.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ecommerce_enableManualPaymentMethodV1 safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ecommerce_enableManualPaymentMethodV1, this is the rule to start with:

ecommerce_enableManualPaymentMethodV1 Rate-limited

ecommerce_enableManualPaymentMethodV1 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ecommerce_enableManualPaymentMethodV1": {
      "limits": [
        {
          "counter": "ecommerce_enablemanualpaymentmethodv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every ecommerce_enableManualPaymentMethodV1 call is checked against it from then on.

FAQ

Questions about ecommerce_enableManualPaymentMethodV1

What does the ecommerce_enableManualPaymentMethodV1 tool do? +

Enable a manual payment method so the store can accept orders without an online payment provider. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does ecommerce_enableManualPaymentMethodV1 accept? +

ecommerce_enableManualPaymentMethodV1 accepts 2 parameters: title, store_id. Required: store_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ecommerce_enableManualPaymentMethodV1? +

Register the Hostinger Api MCP server in PolicyLayer and add a rule for ecommerce_enableManualPaymentMethodV1: 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 Api. Nothing to install.

What risk level is ecommerce_enableManualPaymentMethodV1? +

ecommerce_enableManualPaymentMethodV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ecommerce_enableManualPaymentMethodV1? +

Yes. Add a rate_limit block to the ecommerce_enableManualPaymentMethodV1 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_enableManualPaymentMethodV1 completely? +

Set action: deny in the PolicyLayer policy for ecommerce_enableManualPaymentMethodV1. 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_enableManualPaymentMethodV1? +

ecommerce_enableManualPaymentMethodV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hostinger Api, and thousands of servers like it.

This server

All 258 Hostinger Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →