infomaniak_history
List the destructive actions taken in the current session, most recent first. Each entry includes whether it can be reversed via infomaniak_undo.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-history.md
What infomaniak_history does on Infomaniak Admin
AI agents call infomaniak_history to retrieve information from Infomaniak Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why infomaniak_history is rated Low
This tool performs a pure read operation—it queries and displays a list of destructive actions that were previously taken. It has no side effects, does not create, modify, delete, or execute anything. While it concerns destructive actions, the tool itself merely reports on them; it does not perform them.
From the tool's definition Tool name 'infomaniak_history' and description 'List the destructive actions taken in the current session' indicates a read-only operation that retrieves historical information about past actions without modifying any data.
Attacks that exploit this kind of access
The rule that runs infomaniak_history 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_history, this is the rule to start with:
infomaniak_history is read-only, so it stays allowed. 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_history call is checked against it from then on.
Questions about infomaniak_history
List the destructive actions taken in the current session, most recent first. Each entry includes whether it can be reversed via infomaniak_undo. It is categorised as a Read tool in the Infomaniak Admin MCP Server, which means it retrieves data without modifying state.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_history: 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_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the infomaniak_history 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_history. 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_history 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