infomaniak_api_coverage_report
Fetch the Infomaniak developer portal navigation and report MCP endpoint coverage, admin candidates, risky writes, and user-focused surfaces that are intentionally out of scope.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-api-coverage-report.md
What infomaniak_api_coverage_report does on Infomaniak Admin
AI agents call infomaniak_api_coverage_report 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_api_coverage_report is rated Low
This tool retrieves and reports information about API coverage, endpoints, and administrative surfaces from the developer portal. It performs analysis and reporting on existing data without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal—an agent could only over-report or mischaracterize API endpoints, with no impact on actual systems or data.
From the tool's definition Tool description states 'Fetch the Infomaniak developer portal navigation and report...' — the verb 'Fetch' and 'report' indicate data retrieval with no modification. It queries endpoint coverage metadata and documentation surfaces.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs infomaniak_api_coverage_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_api_coverage_report, this is the rule to start with:
infomaniak_api_coverage_report 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_api_coverage_report call is checked against it from then on.
Questions about infomaniak_api_coverage_report
Fetch the Infomaniak developer portal navigation and report MCP endpoint coverage, admin candidates, risky writes, and user-focused surfaces that are intentionally out of scope. 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_api_coverage_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_api_coverage_report 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_api_coverage_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_api_coverage_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_api_coverage_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