create_class_diagram
AI agents use create_class_diagram to create or update resources in DiagramMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DiagramMCP environment.
The tool creates diagram artifacts (reversible data generation). The empty description lowers confidence somewhat, but the naming pattern and server context clearly indicate this generates a UML class diagram as structured data. This is a Write operation—it produces new content without side effects beyond the diagram itself, and the output can be discarded or regenerated without harm.
From the tool's definition Tool name is 'create_class_diagram'; server description states it 'Enables the dynamic generation of various software development diagrams' and lists similar creation tools (create_architecture_diagram, create_flowchart, etc.)
Attacks that exploit this kind of access
create_class_diagram. It is categorised as a Write tool in the DiagramMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Diagram MCP server in PolicyLayer and add a rule for create_class_diagram: 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 DiagramMCP. Nothing to install.
create_class_diagram 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 create_class_diagram 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 create_class_diagram. 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.
create_class_diagram is provided by the Diagram MCP server (lelondelonmelon/diagrammcp). 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 →