hosting_getInstallationJWTTokenV1

Return a JWT token used to authenticate requests against the specified WordPress installation, including its MCP (Model Context Protocol) endpoint. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id fie...

SERVERHostinger Api SOURCEhostinger-api-mcp

Low RISK CLASS

Category Read

Parameters 22 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/hosting-getinstallationjwttokenv1.md

WHAT IT DOES

What hosting_getInstallationJWTTokenV1 does on Hostinger Api

AI agents call hosting_getInstallationJWTTokenV1 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.

Parameter	Type	Required	Description
`software`	string	Yes	WordPress installation (software) identifier
`username`	string	Yes	username parameter

Parameters from the server's own tool schema.

RISK

Why hosting_getInstallationJWTTokenV1 is rated Low

Although the tool retrieves a sensitive credential (JWT token), it performs no side effects on data or systems—it only queries and returns an existing token. This fits the 'Read' category.

From the tool's definition The tool 'hosting_getInstallationJWTTokenV1' retrieves and returns a JWT authentication token. The description explicitly states 'Return a JWT token' with no modification, deletion, or execution of operations. This is fundamentally a read/retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

hosting_getInstallationJWTTokenV1 Allowed

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

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 hosting_getInstallationJWTTokenV1 call is checked against it from then on.

FAQ

Questions about hosting_getInstallationJWTTokenV1

What does the hosting_getInstallationJWTTokenV1 tool do? +

What parameters does hosting_getInstallationJWTTokenV1 accept? +

hosting_getInstallationJWTTokenV1 accepts 2 parameters: software, username. Required: software, username. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hosting_getInstallationJWTTokenV1? +

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

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

Can I rate-limit hosting_getInstallationJWTTokenV1? +

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

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

hosting_getInstallationJWTTokenV1 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 →