get_module
Get one module's source (files) plus install instructions: write each file under src/modules/{id}/, install its dependencies, and register it in src/modules.ts. The project needs the base first (get_host_scaffold). Large modules come in PAGES: the answer has nextCursor while files remain — call a...
This record as markdown: /tools/com-idosgames-platform/get-module.md
What get_module does on iDos Games
AI agents call get_module 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 |
|---|---|---|---|
id | string | Yes | Module id from list_modules, e.g. store or board-game. |
cursor | integer | — | Index of the first file to return (from nextCursor). Default 0. |
Parameters from the server's own tool schema.
Why get_module is rated Low
Even though get_module 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 get_module 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_module, this is the rule to start with:
get_module 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_module call is checked against it from then on.
Questions about get_module
Get one module's source (files) plus install instructions: write each file under src/modules/{id}/, install its dependencies, and register it in src/modules.ts. The project needs the base first (get_host_scaffold). Large modules come in PAGES: the answer has nextCursor while files remain — call again with the same id and cursor=nextCursor until nextCursor is absent. 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.
get_module accepts 2 parameters: id, cursor. Required: 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_module: 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_module 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_module 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_module. 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_module 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