Save the player
AI agents use save_game_preferences 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 writes/modifies game preference data for players. It affects only the player's personal game settings, not affecting other players or causing irreversible damage, making it Write rather than Destructive. The incomplete description reduces confidence slightly, but the naming pattern and context among sibling game-state management tools confirms it performs a reversible data modification operation.
From the tool's definition Tool named 'save_game_preferences' with description 'Save the player' indicates modification of player preference data stored in game state.
Documented attack patterns abuse exactly the kind of access save_game_preferences 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 save_game_preferences:
{
"version": "1",
"default": "deny",
"tools": {
"save_game_preferences": {
"limits": [
{
"counter": "save_game_preferences_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_game_preferences 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.
Save the player. 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 save_game_preferences: 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.
save_game_preferences 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 save_game_preferences 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 save_game_preferences. 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.
save_game_preferences 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.