approve_sheet_change · DM20 Protocol MCP: Risk & Policy

WHAT IT DOES

What approve_sheet_change does on DM20 Protocol

AI agents use approve_sheet_change 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 approve_sheet_change needs a policy

The tool modifies character sheet state by approving changes, which aligns with Write category (creates or modifies data reversibly). It lacks destructive permanence and doesn't execute arbitrary code or trigger financial transactions. Severity is medium because unauthorized character sheet modifications could disrupt game balance or player data, but the approval workflow and reversibility limit blast radius.

From the tool's definition Tool name 'approve_sheet_change' indicates modification of character sheet data, which is a reversible write operation consistent with D&D campaign management tools. Empty description prevents full certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

approve_sheet_change Rate-limited

approve_sheet_change 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": {
    "approve_sheet_change": {
      "limits": [
        {
          "counter": "approve_sheet_change_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 approve_sheet_change

What does the approve_sheet_change tool do? +

approve_sheet_change. 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 approve_sheet_change? +

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

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

Can I rate-limit approve_sheet_change? +

Yes. Add a rate_limit block to the approve_sheet_change 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 approve_sheet_change completely? +

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

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