infomaniak_update_drive_trash_settings

Update kDrive trash settings through PUT /2/drive/{drive_id}/settings/trash. Two-phase commit with current settings guard.

SERVERInfomaniak Admin SOURCEhenrikogaard/infomaniak-admin-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-update-drive-trash-settings.md

WHAT IT DOES

What infomaniak_update_drive_trash_settings does on Infomaniak Admin

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

RISK

Why infomaniak_update_drive_trash_settings is rated Medium

This tool updates trash settings for a kDrive, which is a reversible modification operation. While it affects storage/retention behavior, the changes can be undone by updating settings again. The two-phase commit pattern mentioned in the server description provides additional safety.

From the tool's definition Tool performs PUT operation to update kDrive trash settings via infomaniak_update_drive_trash_settings. PUT requests modify data. Description explicitly states 'Update' and uses PUT HTTP method, which creates or modifies data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infomaniak_update_drive_trash_settings safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Infomaniak Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infomaniak_update_drive_trash_settings, this is the rule to start with:

infomaniak_update_drive_trash_settings Rate-limited

infomaniak_update_drive_trash_settings 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": {
    "infomaniak_update_drive_trash_settings": {
      "limits": [
        {
          "counter": "infomaniak_update_drive_trash_settings_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 Infomaniak Admin, apply this rule, and every infomaniak_update_drive_trash_settings call is checked against it from then on.

FAQ

Questions about infomaniak_update_drive_trash_settings

What does the infomaniak_update_drive_trash_settings tool do? +

Update kDrive trash settings through PUT /2/drive/{drive_id}/settings/trash. Two-phase commit with current settings guard. It is categorised as a Write tool in the Infomaniak Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on infomaniak_update_drive_trash_settings? +

Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_update_drive_trash_settings: 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 Infomaniak Admin. Nothing to install.

What risk level is infomaniak_update_drive_trash_settings? +

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

Can I rate-limit infomaniak_update_drive_trash_settings? +

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

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

infomaniak_update_drive_trash_settings is provided by the Infomaniak Admin MCP server (henrikogaard/infomaniak-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Infomaniak Admin, and thousands of servers like it.

This server

All 217 Infomaniak Admin tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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