ecommerce_stores_metadata

Get metadata for a store.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/ecommerce-stores-metadata.md

WHAT IT DOES

What ecommerce_stores_metadata does on Hostinger

AI agents call ecommerce_stores_metadata to retrieve information from Hostinger without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ecommerce_stores_metadata is rated Low

This tool queries and retrieves metadata information about an e-commerce store. The verb 'Get' and the read-only nature of metadata retrieval confirm this is a Read operation. No data is created, modified, deleted, or financial operations are performed. The blast radius is minimal since it only exposes informational data.

From the tool's definition Tool name 'ecommerce_stores_metadata' and description 'Get metadata for a store' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ecommerce_stores_metadata 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_stores_metadata, this is the rule to start with:

ecommerce_stores_metadata Allowed

ecommerce_stores_metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ecommerce_stores_metadata": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about ecommerce_stores_metadata

What does the ecommerce_stores_metadata tool do? +

Get metadata for a store. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ecommerce_stores_metadata? +

Register the Hostinger MCP server in PolicyLayer and add a rule for ecommerce_stores_metadata: 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_stores_metadata? +

ecommerce_stores_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ecommerce_stores_metadata? +

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

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

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

KEEP EXPLORING

More on Hostinger, and thousands of servers like it.

This server

All 284 Hostinger tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →