Create a new game with a setting and style
AI agents use create_game to create or update resources in DMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DMCP environment.
This tool creates new game instances, which is a Write operation—it generates and stores new data reversibly. The scope is limited to game state within the RPG system with no real-world impact, external integrations, or destructive capabilities. Severity is low because misuse (creating unwanted games) has minimal blast radius and is easily reversible via deletion of the game instance.
From the tool's definition Tool description explicitly states 'Create a new game' which is a creation operation that generates new data (game instances with setting and style parameters).
Documented attack patterns abuse exactly the kind of access create_game gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_game:
{
"version": "1",
"default": "deny",
"tools": {
"create_game": {
"limits": [
{
"counter": "create_game_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_game stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new game with a setting and style. It is categorised as a Write tool in the DMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the D MCP server in PolicyLayer and add a rule for create_game: 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 DMCP. Nothing to install.
create_game 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 create_game 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 create_game. 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.
create_game is provided by the D MCP server (shawnrushefsky/dmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
204 DMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.