mail_tokens_revoke

Revoke a mail API token.

SERVERHostinger SOURCEidugeni/hostinger-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hostinger-mcp/mail-tokens-revoke.md

WHAT IT DOES

What mail_tokens_revoke does on Hostinger

AI agents call mail_tokens_revoke to permanently remove resources in Hostinger, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why mail_tokens_revoke is rated Critical

Revoking an API token is an irreversible action that immediately invalidates the token, preventing any services or integrations relying on it from functioning. This cannot be undone — a new token must be issued, and any systems using the old token must be reconfigured. This qualifies as Destructive due to its irreversible nature and potentially broad blast radius (breaking mail integrations).

From the tool's definition Revoke a mail API token

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mail_tokens_revoke Hidden

mail_tokens_revoke is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "mail_tokens_revoke"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mail_tokens_revoke

What does the mail_tokens_revoke tool do? +

Revoke a mail API token. It is categorised as a Destructive tool in the Hostinger MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on mail_tokens_revoke? +

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

mail_tokens_revoke is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mail_tokens_revoke? +

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

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

mail_tokens_revoke 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 → Critical-risk tools on this server →

Across the catalogue

web3_revoke_key on 0xarchive →revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →