New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_data_collections

GET ONLY the 'DataCollections' field of TitlePublicConfigurationModel. Data collections - the creator's own data structures, a Firebase/Supabase-like store inside the platform for games, apps and sites. USE A READY PLATFORM MODULE FIRST (currencies, items, store, lootboxes, quests, leaderboards, ...

SERVERiDos Games SOURCEhttps://site.idosgames.com/api/v2/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-idosgames-platform/get-data-collections.md

What get_data_collections does on iDos Games

AI agents call get_data_collections 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.

ParameterTypeRequiredDescription
title_id string Yes TitleID, для которого читаются данные.

Parameters from the server's own tool schema.

Why get_data_collections is rated Low

Even though get_data_collections 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.

Questions about get_data_collections

What does the get_data_collections tool do? +

GET ONLY the 'DataCollections' field of TitlePublicConfigurationModel. Data collections - the creator's own data structures, a Firebase/Supabase-like store inside the platform for games, apps and sites. USE A READY PLATFORM MODULE FIRST (currencies, items, store, lootboxes, quests, leaderboards, chat, social, workshop, match, season, tutorial, localization, push, analytics); declare a collection only for what no module provides (guilds, auctions, orders, catalogs, articles, saved levels, feeds, mail) or for extra data attached to module entities. NEVER store currencies or items inside a record: reference them with a Ref field (Kind Item/Currency/User/…) and move value with Economy (Cost/Grant in engine resource format, charged in the same transaction as the write). Collections maps a collection id (letters, digits, '_', '-', ':' up to 64; a front-end module prefixes its namespace, e.g. 'guild-system:guilds') to: Kind (UserOwned: each record belongs to one user; Shared: records used by many users; Temporary: short-lived, mandatory TTL up to 30 days; Log: append-only, read by time); Mode (Strict = only declared fields); Fields (String, Text = searchable by words, Int, Number, Bool, Date, Json, Array with ItemType, Ref with Ref.Kind, File) with Required/Default (JSON literal)/Min/Max/MaxLength/MaxItems/Enum/Unique/Indexed/Visibility (Everyone/Owner/Server)/ClientWritable=false for server-only fields/Immutable; SortKeys (id + 1..4 components, each a scalar field or createdAt/updatedAt, optionally Descending) - every ordered query uses one, and equality filters on its leading components narrow the range; Access with Read/Create/Update/Delete lists of rules OR-ed together (Anyone - Read only, Authenticated, Owner, Members with MembersField = an Array of Ref(User), Role with a role id from Roles, Server); Limits (MaxItemBytes, MaxItemsPerOwner, TtlSeconds); OnOwnerDeleted (Delete/Anonymize/Keep); Counters (Count or Sum, optional GroupBy - maintained atomically, not allowed for expiring records); Integrations (QuestMetricOnCreate/Update/Delete advance quest objectives with Source ServerApi, AnalyticsEventOn*, TriggerOn* run a CloudCode handler asynchronously); Moderation.BlockedTerms; WriteGate (SegmentGate); PublicViews (published to the CDN for anonymous/site reads: SortKey, optional PartitionField, PageSize, MaxItems, PublishItems) and AnonymousSearch. Queries from a game may filter ONLY by Indexed fields and sort ONLY by declared SortKeys - there are no table scans on the shared cluster. Roles lists title user roles; they are assigned only by CloudCode (server.SetUserRoles) and the dashboard. The count of collections, searchable fields, sort keys, record size and storage are capped by the plan. Records themselves are NOT here - they live in the engine's DataCollection* collections; CloudCode reads and writes them with server.GetDataItem/QueryDataItems/CreateDataItem/UpdateDataItem/DeleteDataItem/BatchDataItems/GetDataCounter. It is categorised as a Read tool in the iDos Games MCP Server, which means it retrieves data without modifying state.

What parameters does get_data_collections accept? +

get_data_collections accepts 1 parameter: title_id. Required: title_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_data_collections? +

Register the iDos Games MCP server in PolicyLayer and add a rule for get_data_collections: 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 get_data_collections? +

get_data_collections is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_data_collections? +

Yes. Add a rate_limit block to the get_data_collections 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 get_data_collections completely? +

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of iDos Games's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.