Security and permissions

• Read-only. Every tool calls read scopes of the public API only, and is annotated readOnlyHint. The MCP server cannot change settings, send events, export raw data or delete anything.
• Least privilege. Use an MCP key: limited to reports:read, realtime:read, config:read and ask, and restricted to the properties you choose. Revoke it at any time in Admin → API keys (or Admin → MCP → Create an MCP key).
• No key storage in hosted mode. The hosted server is stateless: your key travels as a Bearer token on each request, is forwarded to the API for that request only, and is never stored or logged.
• Your plan applies. Questions sent through ask_analytics count toward your monthly AI questions; MCP keys are limited to 120 requests per minute.
• Data minimization. Results are aggregates and session summaries. Eureka never stores IP addresses or form values, so nothing returned by the tools contains them.
• Self-hosted HTTP mode validates the Host and Origin headers against DNS rebinding. When binding to 0.0.0.0, list your public hostname with --allowed-hosts.

What the assistant sees is what you'd see in the app with the same scopes. Data returned to an assistant is processed by that assistant's provider under its own terms: choose the properties you share accordingly.