Rename a tag across all entities in a game
AI agents use rename_tag 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.
The tool modifies game state by renaming tags that presumably apply to NPCs, items, or other entities. This is a write operation as it updates data reversibly. Severity is medium because while it affects multiple entities, the change is not destructive (can be undone by renaming back) and the blast radius in an RPG context is limited to tag organization and entity categorization.
From the tool's definition Tool description states 'Rename a tag across all entities in a game' — this modifies existing data (tag names) across multiple game entities, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access rename_tag 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 rename_tag:
{
"version": "1",
"default": "deny",
"tools": {
"rename_tag": {
"limits": [
{
"counter": "rename_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_tag 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.
Rename a tag across all entities in 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 rename_tag: 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.
rename_tag 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 rename_tag 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 rename_tag. 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.
rename_tag 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.