get_feature_tracking
GET ONLY the 'FeatureTracking' field of TitlePublicConfigurationModel. Feature tracking — which CONCRETE actions are recorded as their own line in the player's FeatureUsage, on top of the default per-module tracking. Entries look like "Character:EquipItems" (module name from the route + the modul...
This record as markdown: /tools/com-idosgames-platform/get-feature-tracking.md
What get_feature_tracking does on iDos Games
AI agents call get_feature_tracking to retrieve information from iDos Games without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
title_id | string | Yes | TitleID, для которого читаются данные. |
Parameters from the server's own tool schema.
Why get_feature_tracking is rated Low
Even though get_feature_tracking only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_feature_tracking 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 get_feature_tracking, this is the rule to start with:
get_feature_tracking 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 iDos Games, apply this rule, and every get_feature_tracking call is checked against it from then on.
Questions about get_feature_tracking
GET ONLY the 'FeatureTracking' field of TitlePublicConfigurationModel. Feature tracking — which CONCRETE actions are recorded as their own line in the player's FeatureUsage, on top of the default per-module tracking. Entries look like "Character:EquipItems" (module name from the route + the module's action name). Purely an analytics setting: it makes those actions selectable as steps in custom funnels (Analytics → Funnels). Tracking starts when an action is added — there is no data for the past, because the action was not recorded then. Capped at 40 entries: every tracked id becomes a key in the player document, which is read on every request. It is categorised as a Read tool in the iDos Games MCP Server, which means it retrieves data without modifying state.
get_feature_tracking accepts 1 parameter: title_id. Required: title_id. The full parameter table on this page comes from the server's own tool schema.
Register the iDos Games MCP server in PolicyLayer and add a rule for get_feature_tracking: 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.
get_feature_tracking 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 get_feature_tracking 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 get_feature_tracking. 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.
get_feature_tracking 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.
More on iDos Games, and thousands of servers like it.
This server
Across the catalogue