import_from_dndbeyond · DM20 Protocol MCP: Risk & Policy

WHAT IT DOES

What import_from_dndbeyond does on DM20 Protocol

AI agents use import_from_dndbeyond to create or update resources in DM20 Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DM20 Protocol environment.

WHY IT NEEDS A POLICY

Why import_from_dndbeyond needs a policy

Import tools create or update existing character data (character sheets, stats, items, spells) based on external sources. While reversible through deletion or re-import, they modify the campaign's character database and could overwrite existing data if not handled carefully. This is a Write operation, not Read (it has side effects) or Destructive (imports are typically additive/reversible).

From the tool's definition Tool name 'import_from_dndbeyond' indicates bulk data ingestion from an external D&D character source. No description provided, but import operations create or modify character records in the local system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_from_dndbeyond Rate-limited

import_from_dndbeyond stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_from_dndbeyond": {
      "limits": [
        {
          "counter": "import_from_dndbeyond_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DM20 Protocol, so you can run agents against it safely.

FAQ

Questions about import_from_dndbeyond

What does the import_from_dndbeyond tool do? +

import_from_dndbeyond. It is categorised as a Write tool in the DM20 Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_from_dndbeyond? +

Register the DM20 Protocol MCP server in PolicyLayer and add a rule for import_from_dndbeyond: 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.

What risk level is import_from_dndbeyond? +

import_from_dndbeyond is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_from_dndbeyond? +

Yes. Add a rate_limit block to the import_from_dndbeyond 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.

How do I block import_from_dndbeyond completely? +

Set action: deny in the PolicyLayer policy for import_from_dndbeyond. 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.

What MCP server provides import_from_dndbeyond? +

import_from_dndbeyond 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.