Complete scene transition in one call: moves specified characters to a new location and logs a narrative event. Perfect for moving between scenes.
AI agents use scene_transition 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 repositioning characters and creating a log entry. These are reversible data modifications within a game context, making it a Write operation. No code execution, deletion, or financial transactions are involved. The blast radius is low since misuse only affects a fictional game state.
From the tool's definition moves specified characters to a new location and logs a narrative event
Documented attack patterns abuse exactly the kind of access scene_transition 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 scene_transition:
{
"version": "1",
"default": "deny",
"tools": {
"scene_transition": {
"limits": [
{
"counter": "scene_transition_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}scene_transition 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.
Complete scene transition in one call: moves specified characters to a new location and logs a narrative event. Perfect for moving between scenes. 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 scene_transition: 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.
scene_transition 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 scene_transition 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 scene_transition. 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.
scene_transition 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.