list_my_titles
List the games (Titles) this connection may work with: TitleID, name, publication status and the permissions granted on each — call it first when the user names a game or says "my game", then pass its TitleID as title_id to the other tools. A game's sandbox copy is a separate Title (DevTitleID) w...
This record as markdown: /tools/com-idosgames-platform/list-my-titles.md
What list_my_titles does on iDos Games
AI agents call list_my_titles 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 |
|---|---|---|---|
skip | integer | — | How many games to skip (paging). Default 0. |
limit | integer | — | Page size, default 50, max 60. |
search | string | — | Optional substring of the game's name or TitleID. |
Parameters from the server's own tool schema.
Why list_my_titles is rated Low
Even though list_my_titles 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.
Attacks that exploit this kind of access
The rule that runs list_my_titles 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 list_my_titles, this is the rule to start with:
list_my_titles 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 list_my_titles call is checked against it from then on.
Questions about list_my_titles
List the games (Titles) this connection may work with: TitleID, name, publication status and the permissions granted on each — call it first when the user names a game or says "my game", then pass its TitleID as title_id to the other tools. A game's sandbox copy is a separate Title (DevTitleID) with its own permissions (DevAccess); an empty Access means the live game itself is not granted. Filter by name or id with "search"; long lists are paged (skip/limit, HasMore). Read-only; takes no title_id. It is categorised as a Read tool in the iDos Games MCP Server, which means it retrieves data without modifying state.
list_my_titles accepts 3 parameters: skip, limit, search. 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 list_my_titles: 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.
list_my_titles 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 list_my_titles 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 list_my_titles. 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.
list_my_titles 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