list_modules
List the composable iDos Games game modules in the catalog — the same registry the local @idosgames/mcp server serves. Each entry has id, name, type (template = a complete ready-to-run game to start FROM, e.g. voxelcraft; feature = a system to add on top, e.g. store, quests, leaderboard), engine,...
This record as markdown: /tools/com-idosgames-platform/list-modules.md
What list_modules does on iDos Games
AI agents call list_modules 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.
Why list_modules is rated Low
Even though list_modules 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 list_modules 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_modules, this is the rule to start with:
list_modules 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_modules call is checked against it from then on.
Questions about list_modules
List the composable iDos Games game modules in the catalog — the same registry the local @idosgames/mcp server serves. Each entry has id, name, type (template = a complete ready-to-run game to start FROM, e.g. voxelcraft; feature = a system to add on top, e.g. store, quests, leaderboard), engine, genre, a short summary, what it 'provides' (its features), tags, preview media, a live demo url, 'inBase' (installed with the base in every new project), 'uses' (modules a game needs) and 'events' (topics it emits and listens to). Read 'provides' to reuse a ready module instead of building the feature from scratch, then get_module to pull its source. 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.
Register the iDos Games MCP server in PolicyLayer and add a rule for list_modules: 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_modules 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_modules 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_modules. 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_modules 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