AI agents use create_note 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 data within the game state but does not execute external code, delete data irreversibly, or affect real-world systems. It is a straightforward write operation with minimal blast radius—at worst, an agent could spam notes, but this is easily remediated. Low severity assigned due to the scoped, non-destructive, and non-external nature of the operation.
From the tool's definition Tool name 'create_note' and description 'Create a game note' indicate data creation. The context is a dungeon master RPG server managing game state, where notes are game-scoped metadata. The action is reversible (notes can be deleted or modified).
Documented attack patterns abuse exactly the kind of access create_note 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 create_note:
{
"version": "1",
"default": "deny",
"tools": {
"create_note": {
"limits": [
{
"counter": "create_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_note 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.
Create a game note. 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 create_note: 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.
create_note 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 create_note 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 create_note. 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.
create_note 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.