This record as markdown: /tools/hostinger-mcp/wp-login-link.md
What wp_login_link does on Hostinger
AI agents use wp_login_link to create or update resources in Hostinger, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger environment.
Why wp_login_link is rated Medium
Creating a login link is a write operation that generates new authentication credentials or access tokens. While not destructive (links can be revoked/invalidated), it creates sensitive data that grants admin access to WordPress installations.
From the tool's definition Tool creates a one-click WP admin login link. The name 'wp_login_link' and description 'Create a' indicate this tool generates (creates) a new authentication artifact—a login link—which is a reversible data creation action.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs wp_login_link 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_login_link, this is the rule to start with:
wp_login_link 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger, apply this rule, and every wp_login_link call is checked against it from then on.
Questions about wp_login_link
Create a one-click WP admin login link. It is categorised as a Write tool in the Hostinger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hostinger MCP server in PolicyLayer and add a rule for wp_login_link: 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_login_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wp_login_link 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_login_link. 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_login_link 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