Regenerate all character sheets for the current campaign.
AI agents use sync_all_sheets 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.
Regenerating all character sheets implies overwriting/updating existing data for all characters in the campaign. This is a bulk Write operation — it modifies data but is likely reversible (sheets can be regenerated again). However, the blast radius is medium because it affects all characters at once, and unintended regeneration could overwrite manual customizations or current state.
From the tool's definition Regenerate all character sheets for the current campaign
Attacks that exploit this kind of access
Regenerate all character sheets for the current campaign. 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.
Register the DM20 Protocol MCP server in PolicyLayer and add a rule for sync_all_sheets: 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.
sync_all_sheets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sync_all_sheets 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 sync_all_sheets. 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.
sync_all_sheets 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 →