Get monster stat block from loaded rulebooks.
AI agents call get_monster_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 and retrieves monster statistics from pre-loaded rulebook data. It performs a read-only lookup operation without creating, modifying, deleting, or executing anything. The action is informational retrieval typical of a D&D reference tool. No financial, destructive, or code execution capability is present. Severity is low because misuse would only expose game mechanics reference data.
From the tool's definition Tool name 'get_monster_info' and description 'Get monster stat block from loaded rulebooks' indicate retrieval of existing data from rulebooks with no modification or side effects.
Attacks that exploit this kind of access
Get monster stat block 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_monster_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_monster_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_monster_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_monster_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_monster_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 →