search_modules
Keyword search across modules and skills. Matches a module on its id, name, type, engine, genre, summary, description, what it 'provides' and tags — so you can find a ready module by the feature you need (e.g. 'dice board', 'idle income', 'daily reward') rather than by name. Skills match on name ...
This record as markdown: /tools/com-idosgames-platform/search-modules.md
What search_modules does on iDos Games
AI agents call search_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Free-text query; every word must match. |
Parameters from the server's own tool schema.
Why search_modules is rated Low
Even though search_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.
Attacks that exploit this kind of access
The rule that runs search_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 search_modules, this is the rule to start with:
search_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 search_modules call is checked against it from then on.
Questions about search_modules
Keyword search across modules and skills. Matches a module on its id, name, type, engine, genre, summary, description, what it 'provides' and tags — so you can find a ready module by the feature you need (e.g. 'dice board', 'idle income', 'daily reward') rather than by name. Skills match on name and description. Returns the matching catalog entries. 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.
search_modules accepts 1 parameter: query. Required: query. 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 search_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.
search_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 search_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 search_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.
search_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