AI agents call load_campaign to retrieve information from D&D MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves campaign data for display or use without creating, modifying, deleting, or executing operations. It is a straightforward read operation with no side effects. Severity is low because misuse would only expose existing campaign data, not cause damage or unauthorized changes.
From the tool's definition Tool name 'load_campaign' and description 'Load a specific campaign' indicate data retrieval with no modification. The verb 'load' implies fetching or retrieving an existing campaign state.
Documented attack patterns abuse exactly the kind of access load_campaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and D&D MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for load_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"load_campaign": {}
}
}load_campaign is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Load a specific campaign. It is categorised as a Read tool in the D&D MCP Server MCP Server, which means it retrieves data without modifying state.
Register the D&D MCP Server 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 D&D MCP Server. 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 D&D MCP Server MCP server (study-flamingo/gamemaster-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from D&D MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 D&D MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.