List all discovered engine modules with metadata — labels, doc counts, engines, and sections. Use to understand what knowledge is available across engines and find the right module for a project.
AI agents call list_modules to retrieve information from Gamedev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a query/listing operation to expose metadata about game development knowledge modules. This is purely informational with no side effects, no code execution, no data modification, and no destructive actions. It aligns with the Read category as defined: 'retrieves or queries data; no side effects (search, list, get, fetch).'
From the tool's definition Tool description states it 'List[s] all discovered engine modules with metadata' — a read-only operation that retrieves and presents information about available modules without creating, modifying, or deleting any data.
Attacks that exploit this kind of access
List all discovered engine modules with metadata — labels, doc counts, engines, and sections. Use to understand what knowledge is available across engines and find the right module for a project. It is categorised as a Read tool in the Gamedev MCP Server, which means it retrieves data without modifying state.
Register the Gamedev 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 Gamedev. 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 Gamedev MCP server (sbenson2/gamedev-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →