party_knowledge
AI agents call party_knowledge 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.
The name implies reading knowledge about the party (character states, session history, lore) rather than modifying or executing actions. No language suggests side effects, deletions, or external execution. The empty description lowers confidence slightly, but the pattern of sibling tools and D&D domain context supports a Read classification.
From the tool's definition Tool name 'party_knowledge' suggests retrieval of game state information. The description is empty, but based on sibling tools like 'ask_books' (query), 'build_encounter_tool' (read), and the server's stated purpose of 'querying personal PDF rulebooks using…
Attacks that exploit this kind of access
party_knowledge. 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 party_knowledge: 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.
party_knowledge 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 party_knowledge 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 party_knowledge. 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.
party_knowledge 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.
party_knowledge is one line of DM20 Protocol's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →