infomaniak_create_drive_activity_report
Create a kDrive activity report. Two-phase confirmation is required because Infomaniak starts report generation asynchronously.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-create-drive-activity-report.md
What infomaniak_create_drive_activity_report does on Infomaniak Admin
AI agents use infomaniak_create_drive_activity_report 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.
Why infomaniak_create_drive_activity_report is rated Medium
This tool creates a new report object/resource, which is a reversible write operation. Although report generation is asynchronous and the two-phase confirmation adds safety controls, the action itself generates new data.
From the tool's definition The tool name contains "create" and the description states it will "Create a kDrive activity report." The description confirms this is a write operation that generates new data (a report) asynchronously.
Attacks that exploit this kind of access
The rule that runs infomaniak_create_drive_activity_report 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_create_drive_activity_report, this is the rule to start with:
infomaniak_create_drive_activity_report 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 Infomaniak Admin, apply this rule, and every infomaniak_create_drive_activity_report call is checked against it from then on.
Questions about infomaniak_create_drive_activity_report
Create a kDrive activity report. Two-phase confirmation is required because Infomaniak starts report generation asynchronously. 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.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_create_drive_activity_report: 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.
infomaniak_create_drive_activity_report 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 infomaniak_create_drive_activity_report 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 infomaniak_create_drive_activity_report. 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.
infomaniak_create_drive_activity_report 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.
More on Infomaniak Admin, and thousands of servers like it.
This server
Across the catalogue