AI agents use add_session_note 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.
The tool appends or creates notes associated with a D&D campaign session, a reversible operation that modifies campaign state but cannot irreversibly destroy data or execute arbitrary code. Without a description, confidence is moderate. The 'add' prefix and comparison to sibling Write-category tools (add_item_to_character, add_event) support Write classification.
From the tool's definition Tool name 'add_session_note' indicates creation/modification of session notes. Description is empty, requiring inference from context and sibling tools which include create_campaign, create_character, add_item_to_character, add_event—all Write operations.
Documented attack patterns abuse exactly the kind of access add_session_note 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 add_session_note:
{
"version": "1",
"default": "deny",
"tools": {
"add_session_note": {
"limits": [
{
"counter": "add_session_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_session_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.
add_session_note. 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 add_session_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 D&D MCP Server. Nothing to install.
add_session_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 add_session_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 add_session_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.
add_session_note 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.