mail_updateForwarderKeepCopySettingV1

Enable or disable keeping a copy of forwarded messages in the mailbox.

SERVERHostinger Api SOURCEhostinger-api-mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/mail-updateforwarderkeepcopysettingv1.md

WHAT IT DOES

What mail_updateForwarderKeepCopySettingV1 does on Hostinger Api

AI agents use mail_updateForwarderKeepCopySettingV1 to create or update resources in Hostinger Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hostinger Api environment.

Parameter	Type	Required	Description
`forwarderId`	string	Yes	Forwarder resource ID
`is_keep_copy_enabled`	boolean	Yes	Whether to keep a copy of forwarded messages in the mailbox

Parameters from the server's own tool schema.

RISK

Why mail_updateForwarderKeepCopySettingV1 is rated Medium

This tool modifies email configuration settings (forwarding behavior) but does not delete data or cause irreversible changes. The action is reversible: the setting can be toggled back. This is a Write operation because it creates or modifies data (email forwarding preferences).

From the tool's definition Tool name contains 'update' and description states 'Enable or disable keeping a copy of forwarded messages' — this modifies email forwarding settings reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mail_updateForwarderKeepCopySettingV1 Rate-limited

mail_updateForwarderKeepCopySettingV1 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail_updateForwarderKeepCopySettingV1": {
      "limits": [
        {
          "counter": "mail_updateforwarderkeepcopysettingv1_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mail_updateForwarderKeepCopySettingV1

What does the mail_updateForwarderKeepCopySettingV1 tool do? +

Enable or disable keeping a copy of forwarded messages in the mailbox. It is categorised as a Write tool in the Hostinger Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does mail_updateForwarderKeepCopySettingV1 accept? +

mail_updateForwarderKeepCopySettingV1 accepts 2 parameters: forwarderId, is_keep_copy_enabled. Required: forwarderId, is_keep_copy_enabled. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mail_updateForwarderKeepCopySettingV1? +

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

mail_updateForwarderKeepCopySettingV1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mail_updateForwarderKeepCopySettingV1? +

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

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

mail_updateForwarderKeepCopySettingV1 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 382 Hostinger Api tools →

Across the catalogue

mail_create_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →