Load a specific campaign.
AI agents call load_campaign 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 performs a data retrieval operation with no side effects. It accesses and displays campaign information but does not create, modify, delete, or execute any game mechanics or external operations. The blast radius of misuse is minimal—an attacker could view unauthorized campaign data, but cannot alter game state, delete campaigns, or trigger irreversible actions. This is classified as Read with low severity.
From the tool's definition The tool name 'load_campaign' and description indicate it retrieves and opens a campaign from storage. The verb 'load' is a read operation that retrieves existing data without modifying, creating, or deleting it.
Attacks that exploit this kind of access
Load a specific campaign. 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 load_campaign: 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.
load_campaign 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 load_campaign 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 load_campaign. 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.
load_campaign 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 →