Update a game's name, description, or visibility. Requires authentication.
Part of the The Game Crafter server.
Free to start. No card required.
AI agents use update_game to create or modify resources in The Game Crafter. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_game repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach The Game Crafter.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"update_game": {
"limits": [
{
"counter": "update_game_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full The Game Crafter policy for all 14 tools.
These attack patterns abuse exactly the kind of access update_game gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Update a game's name, description, or visibility. Requires authentication.. It is categorised as a Write tool in the The Game Crafter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the The Game Crafter MCP server in PolicyLayer and add a rule for update_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 The Game Crafter. Nothing to install.
update_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 update_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 update_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.
update_game is provided by the The Game Crafter MCP server (@alex-gon/tgc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 The Game Crafter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.