add_spell
AI agents use add_spell to create or update resources in DM20 Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DM20 Protocol environment.
This tool creates or modifies character spell lists, which is reversible game state manipulation. It fits the Write category (creates or modifies data reversibly). Severity is medium because misuse could disrupt campaign balance or give unfair character advantages, but effects are confined to a game session and can be corrected by a DM.
From the tool's definition Tool name 'add_spell' and context of D&D campaign management system with character sheet modifications ('add_item_to_character', 'approve_sheet_change' as sibling tools). The 'add_' prefix indicates creation/modification of game data.
Attacks that exploit this kind of access
add_spell. It is categorised as a Write tool in the DM20 Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DM20 Protocol MCP server in PolicyLayer and add a rule for add_spell: 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 DM20 Protocol. Nothing to install.
add_spell 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_spell 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_spell. 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_spell is provided by the DM20 Protocol MCP server (polloinfilzato/dm20-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →