Get spell details from loaded rulebooks.
AI agents call get_spell_info to retrieve information from DM20 Protocol without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries pre-loaded rulebook data to retrieve spell information. It is purely informational with no side effects—no data is created, modified, deleted, or executed. The action is a simple lookup operation typical of Read category tools. The context (D&D campaign management) is domain-specific but does not change the fundamental nature of the operation.
From the tool's definition Tool name 'get_spell_info' and description 'Get spell details from loaded rulebooks' indicate retrieval of static game data with no modification, creation, deletion, or execution capability.
Attacks that exploit this kind of access
Get spell details from loaded rulebooks. It is categorised as a Read tool in the DM20 Protocol MCP Server, which means it retrieves data without modifying state.
Register the DM20 Protocol MCP server in PolicyLayer and add a rule for get_spell_info: 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.
get_spell_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_spell_info 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 get_spell_info. 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.
get_spell_info 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 →