infomaniak_list_teams_and_tags
List the teams (with owners + user/product counts) AND the tags (with products carrying each tag) of an organization, in a single call. Both are useful to understand how an org partitions access and labels its products. Manager-private.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-list-teams-and-tags.md
What infomaniak_list_teams_and_tags does on Infomaniak Admin
AI agents call infomaniak_list_teams_and_tags 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_list_teams_and_tags is rated Low
This is a read-only operation that retrieves organizational structure and labeling information. It neither creates, modifies, deletes, executes code, nor involves financial transactions. The 'Manager-private' designation indicates access control but does not change the nature of the operation from read-only. Blast radius is limited to information disclosure.
From the tool's definition Tool name contains 'list' and description states 'List the teams... AND the tags... in a single call.' The function retrieves and queries organizational metadata (teams with owners/counts, tags with associated products) with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs infomaniak_list_teams_and_tags 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_list_teams_and_tags, this is the rule to start with:
infomaniak_list_teams_and_tags 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_list_teams_and_tags call is checked against it from then on.
Questions about infomaniak_list_teams_and_tags
List the teams (with owners + user/product counts) AND the tags (with products carrying each tag) of an organization, in a single call. Both are useful to understand how an org partitions access and labels its products. Manager-private. 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_list_teams_and_tags: 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_list_teams_and_tags 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_list_teams_and_tags 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_list_teams_and_tags. 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_list_teams_and_tags 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