save_analytics

SERVERiDos Games SOURCEhttps://site.idosgames.com/api/v2/mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-idosgames-platform/save-analytics.md

WHAT IT DOES

What save_analytics does on iDos Games

AI agents use save_analytics to create or update resources in iDos Games, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your iDos Games environment.

Parameter	Type	Required	Description
`value`	object	Yes	Custom events (Firebase Analytics parity). Everything here is chosen by the publisher within their plan's analytics limits. Absent section or Enabled != true =
`title_id`	string	Yes	TitleID, для которого сохраняются данные.

Parameters from the server's own tool schema.

RISK

Why save_analytics is rated Medium

An AI agent can call save_analytics faster than any human can review: one bad instruction and it creates or modifies resources in iDos Games by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs save_analytics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and iDos Games, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_analytics, this is the rule to start with:

save_analytics Rate-limited

save_analytics 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_analytics": {
      "limits": [
        {
          "counter": "save_analytics_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect iDos Games, apply this rule, and every save_analytics call is checked against it from then on.

FAQ

Questions about save_analytics

What does the save_analytics tool do? +

PARTIAL SAVE: writes ONLY the 'Analytics' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Custom events - Firebase Analytics parity. The game sends its own events (logEvent(name, params, value)); the engine stores them per player per UTC day and the dashboard reports counts, unique players, value sums and breakdowns by platform, app version, OS, device, language, country, new/returning and acquisition source; A/B experiment goals and custom funnel steps can use these events. Enabled is the master switch and defaults to OFF. EventNaming: "Open" (any valid name is accepted and joins the title's event catalog up to the PLAN limit) or "Declared" (only names listed in Events). Events maps an event name (^[A-Za-z][A-Za-z0-9_]{0,39}$; prefixes idos_/firebase_/google_/ga_ are reserved, except the automatic idos_* events) to a display name, description and a Blocked flag. Dimensions registers event parameters as reporting dimensions (like GA4 custom dimensions) - the count is capped by the plan; unregistered parameters are accepted but not stored. RetentionDays is how long per-player event data is kept (default 90, capped by the plan); daily title summaries are kept forever. AutomaticEvents (default on) accepts the SDK's automatic events: idos_first_open, idos_session_start, idos_app_update, idos_os_update, idos_screen_view. It is categorised as a Write tool in the iDos Games MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does save_analytics accept? +

save_analytics accepts 2 parameters: value, title_id. Required: value, title_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on save_analytics? +

Register the iDos Games MCP server in PolicyLayer and add a rule for save_analytics: 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 iDos Games. Nothing to install.

What risk level is save_analytics? +

save_analytics is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_analytics? +

Yes. Add a rate_limit block to the save_analytics 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.

How do I block save_analytics completely? +

Set action: deny in the PolicyLayer policy for save_analytics. 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.

What MCP server provides save_analytics? +

save_analytics is provided by the iDos Games MCP server (https://site.idosgames.com/api/v2/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on iDos Games, and thousands of servers like it.

This server

All 159 iDos Games tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →