This record as markdown: /tools/hostinger-mcp/wp-jwt-token.md
What wp_jwt_token does on Hostinger
AI agents call wp_jwt_token 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.
Why wp_jwt_token is rated Low
This tool retrieves a JWT token for authentication purposes—a read operation that queries system state to obtain credentials. While the token itself could be misused downstream, the tool itself performs no side effects beyond returning data. It does not execute code, modify data, delete resources, or commit financial transactions.
From the tool's definition Tool name 'wp_jwt_token' and description 'Get installation JWT token for API access' indicate retrieval of an authentication token. The verb 'Get' is explicitly used, and no modification or execution is described.
Attacks that exploit this kind of access
The rule that runs wp_jwt_token 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 wp_jwt_token, this is the rule to start with:
wp_jwt_token is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every wp_jwt_token call is checked against it from then on.
Questions about wp_jwt_token
Get installation JWT token for API access. It is categorised as a Read tool in the Hostinger MCP Server, which means it retrieves data without modifying state.
Register the Hostinger MCP server in PolicyLayer and add a rule for wp_jwt_token: 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.
wp_jwt_token is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wp_jwt_token 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.
Set action: deny in the PolicyLayer policy for wp_jwt_token. 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.
wp_jwt_token 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.
This server
Across the catalogue