Add an entry to the combat log
AI agents use add_combat_log 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 or appends a new entry to a combat log, which is a reversible write operation within the game state. It modifies data (the log) but does not execute arbitrary code, delete data permanently, or affect external systems. The blast radius is limited to the game session state.
From the tool's definition Tool name 'add_combat_log' and description 'Add an entry to the combat log' indicates creation/modification of game state data in a structured log.
Documented attack patterns abuse exactly the kind of access add_combat_log 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 add_combat_log:
{
"version": "1",
"default": "deny",
"tools": {
"add_combat_log": {
"limits": [
{
"counter": "add_combat_log_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_combat_log 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.
Add an entry to the combat log. 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 add_combat_log: 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.
add_combat_log 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 add_combat_log 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 add_combat_log. 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.
add_combat_log 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.