create_use_case_diagram
AI agents use create_use_case_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.
This tool creates new UML diagram objects within StarUML, which constitutes reversible data creation/modification (Write category). Severity is medium because misuse could generate unwanted diagrams cluttering a project, but the effects are fully reversible through deletion.
From the tool's definition Tool name 'create_use_case_diagram' indicates it creates diagram artifacts. Server description confirms tools 'generate diagrams' and 'create_*_diagram' variants that modify StarUML project state. No description provided for this specific tool.
Attacks that exploit this kind of access
create_use_case_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_use_case_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_use_case_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_use_case_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_use_case_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_use_case_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 →