Log a narrative event. CRITICAL: Call this after EVERY significant narrative beat - dialogue exchanges, player actions, combat rounds, discoveries, travel, decisions. This is the primary way to preserve game history. Event types:
AI agents use log_event 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 writes narrative event entries to a game log/history. It creates new records but does not delete data, execute code, move money, or perform irreversible destructive actions. Misuse potential is low — worst case is spamming log entries or recording incorrect narrative history, which is reversible in principle.
From the tool's definition 'Log a narrative event' and 'primary way to preserve game history' — creates/stores event records in game state
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access log_event 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 log_event:
{
"version": "1",
"default": "deny",
"tools": {
"log_event": {
"limits": [
{
"counter": "log_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}log_event 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.
Log a narrative event. CRITICAL: Call this after EVERY significant narrative beat - dialogue exchanges, player actions, combat rounds, discoveries, travel, decisions. This is the primary way to preserve game history. Event types:. 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 log_event: 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.
log_event 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 log_event 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 log_event. 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.
log_event 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.