Set or remove the title image for a game
AI agents use set_game_title_image 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 modifies game state by writing a title image association, but the change is non-destructive and reversible. It does not execute code, delete data irreversibly, or move money. The scope is limited to cosmetic/presentational game metadata, presenting minimal blast radius if misused.
From the tool's definition Tool description states 'Set or remove the title image for a game' — a write operation that creates or modifies game metadata (the title image reference). The action is reversible (can be removed or changed).
Documented attack patterns abuse exactly the kind of access set_game_title_image 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 set_game_title_image:
{
"version": "1",
"default": "deny",
"tools": {
"set_game_title_image": {
"limits": [
{
"counter": "set_game_title_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_game_title_image 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.
Set or remove the title image for a game. 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 set_game_title_image: 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.
set_game_title_image 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 set_game_title_image 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 set_game_title_image. 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.
set_game_title_image 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.