AI agents use end_combat to create or update resources in D&D MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your D&D MCP Server environment.
Ending a combat encounter modifies the state of the campaign (marks the encounter as finished, potentially updates character/NPC statuses), but this is reversible in the context of a campaign management system — sessions and encounters can be recreated or re-opened. It is a state change (Write), not a destructive deletion. Severity is medium because misuse could disrupt an active session's combat state.
From the tool's definition End the current combat encounter
Documented attack patterns abuse exactly the kind of access end_combat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and D&D MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for end_combat:
{
"version": "1",
"default": "deny",
"tools": {
"end_combat": {
"limits": [
{
"counter": "end_combat_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}end_combat 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.
End the current combat encounter. It is categorised as a Write tool in the D&D MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the D&D MCP Server MCP server in PolicyLayer and add a rule for end_combat: 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 D&D MCP Server. Nothing to install.
end_combat 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 end_combat 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 end_combat. 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.
end_combat is provided by the D&D MCP Server MCP server (study-flamingo/gamemaster-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from D&D MCP Server, 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.
30 D&D MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.