get_host_scaffold
Get the base every NEW project starts from — the host shell with sign-in and the lobby (index.html, main.tsx, src/app.config.ts, the wallet files, an empty src/modules.ts, config; the lobby and sign-in come from @idosgames/app-shell). Write these files to the project root, install the versions fr...
This record as markdown: /tools/com-idosgames-platform/get-host-scaffold.md
What get_host_scaffold does on iDos Games
AI agents call get_host_scaffold 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 get_host_scaffold is rated Low
Even though get_host_scaffold 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 · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_host_scaffold 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_host_scaffold, this is the rule to start with:
get_host_scaffold 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_host_scaffold call is checked against it from then on.
Questions about get_host_scaffold
Get the base every NEW project starts from — the host shell with sign-in and the lobby (index.html, main.tsx, src/app.config.ts, the wallet files, an empty src/modules.ts, config; the lobby and sign-in come from @idosgames/app-shell). Write these files to the project root, install the versions from get_manifest, then add modules with get_module: the systems with inBase, the game(s) with the modules each game 'uses', and any other system the app needs. 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 get_host_scaffold: 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_host_scaffold 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_host_scaffold 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_host_scaffold. 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_host_scaffold 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