reach_listProfilesV1

This endpoint returns all profiles available to the client, including their basic information.

SERVERHostinger Api SOURCEhostinger-api-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/io-github-hostinger-hostinger-api-mcp/reach-listprofilesv1.md

WHAT IT DOES

What reach_listProfilesV1 does on Hostinger Api

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

RISK

Why reach_listProfilesV1 is rated Low

This tool queries and retrieves profile data. It performs no creation, modification, deletion, or code execution. The blast radius of misuse is limited to information disclosure of profile metadata that the authenticated client can already access.

From the tool's definition Tool name contains 'list' and description states it 'returns all profiles available to the client, including their basic information' — a data retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

reach_listProfilesV1 Allowed

reach_listProfilesV1 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": {
    "reach_listProfilesV1": {}
  }
}

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

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

FAQ

Questions about reach_listProfilesV1

What does the reach_listProfilesV1 tool do? +

This endpoint returns all profiles available to the client, including their basic information. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on reach_listProfilesV1? +

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

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

Can I rate-limit reach_listProfilesV1? +

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

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

reach_listProfilesV1 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

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