Auto-generate a game recap note from recent narrative events
AI agents use generate_recap 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.
The tool generates and writes a recap note based on recent game events. It creates new data (a recap note) from existing narrative events, making it a Write operation. It has low blast radius as it only affects game state within a text-based RPG system and is reversible.
From the tool's definition Auto-generate a game recap note from recent narrative events
Documented attack patterns abuse exactly the kind of access generate_recap 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 generate_recap:
{
"version": "1",
"default": "deny",
"tools": {
"generate_recap": {
"limits": [
{
"counter": "generate_recap_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_recap 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.
Auto-generate a game recap note from recent narrative events. 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 generate_recap: 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.
generate_recap 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 generate_recap 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 generate_recap. 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.
generate_recap 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.