Complete combat setup in one call: creates enemy NPCs and starts combat with all participants (enemies + players at location). Returns the ready-to-play combat state.
AI agents use setup_combat_encounter 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 creates new NPC entities and initializes a combat encounter state, which are reversible write operations within the game state management system. It does not execute arbitrary code, destroy data irreversibly, or involve financial transactions. The blast radius is medium as misuse could disrupt ongoing game state but within a sandboxed RPG context.
From the tool's definition creates enemy NPCs and starts combat with all participants
Documented attack patterns abuse exactly the kind of access setup_combat_encounter 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 setup_combat_encounter:
{
"version": "1",
"default": "deny",
"tools": {
"setup_combat_encounter": {
"limits": [
{
"counter": "setup_combat_encounter_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setup_combat_encounter 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 combat setup in one call: creates enemy NPCs and starts combat with all participants (enemies + players at location). Returns the ready-to-play combat state. 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 setup_combat_encounter: 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.
setup_combat_encounter 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 setup_combat_encounter 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 setup_combat_encounter. 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.
setup_combat_encounter 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.