bulk_update_characters
AI agents use bulk_update_characters 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.
The 'bulk_update_characters' tool performs reversible modifications to character data (Write category). Severity is high because bulk operations can affect multiple character records simultaneously, creating significant blast radius if an AI agent misuses it (e.g., corrupting stats for multiple characters).
From the tool's definition Tool name 'bulk_update_characters' indicates bulk modification of character data. Description is empty, limiting certainty.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
bulk_update_characters. 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 bulk_update_characters: 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.
bulk_update_characters 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 bulk_update_characters 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 bulk_update_characters. 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.
bulk_update_characters 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 →