create_er_diagram
AI agents use create_er_diagram to create or update resources in StarUML MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your StarUML MCP Server environment.
Based on the naming pattern consistent with sibling tools (create_activity_diagram, create_class_diagram, etc.) and the server's purpose of generating UML diagrams, this tool likely creates an ER diagram in StarUML. 'Create' implies writing/generating new content. The description is empty, which lowers confidence, but the pattern strongly suggests a Write action.
From the tool's definition Tool name 'create_er_diagram' and server context: 'Enables AI to remotely control StarUML for generating UML diagrams (use case, class, sequence, ER, etc.)'
Attacks that exploit this kind of access
create_er_diagram. It is categorised as a Write tool in the StarUML MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the StarUML MCP Server MCP server in PolicyLayer and add a rule for create_er_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 StarUML MCP Server. Nothing to install.
create_er_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_er_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_er_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_er_diagram is provided by the StarUML MCP Server MCP server (stonesho/staruml_mcp). 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 →