Use when: creating a GDD, planning phases, evaluating scope, preparing to launch or market a game, choosing architecture patterns. Plan and ship your game. Actions: gdd, phase, scope_check, launch, store_page, pricing, marketing, trailer, patterns.
AI agents use design to create or update resources in GameCodex — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GameCodex environment.
This tool primarily creates and writes structured planning documents (Game Design Documents, phase plans, store pages, marketing materials). The outputs are generated content artifacts rather than code execution or destructive operations.
From the tool's definition 'creating a GDD, planning phases, evaluating scope, preparing to launch or market a game, choosing architecture patterns' and actions: 'gdd, phase, scope_check, launch, store_page, pricing, marketing, trailer, patterns'
Attacks that exploit this kind of access
Use when: creating a GDD, planning phases, evaluating scope, preparing to launch or market a game, choosing architecture patterns. Plan and ship your game. Actions: gdd, phase, scope_check, launch, store_page, pricing, marketing, trailer, patterns. It is categorised as a Write tool in the GameCodex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GameCodex MCP server in PolicyLayer and add a rule for design: 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 GameCodex. Nothing to install.
design is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the design 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 design. 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.
design is provided by the GameCodex MCP server (wesleysalzer/gamecodex). 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 →