create_flowchart
AI agents use create_flowchart 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.
Creating a flowchart in StarUML is a Write operation—it generates a new diagram artifact that can be modified or deleted later, but the operation itself is reversible and causes no destructive side effects. Severity is low because misuse results in temporary artifacts without damage to underlying systems or data. Confidence is reduced slightly due to empty description, but the pattern is clear from sibling tools.
From the tool's definition Tool name 'create_flowchart' indicates diagram creation; sibling tools like 'create_class_diagram', 'create_sequence_diagram' all create artifacts in StarUML. Description is empty, so inference is based on naming pattern and context.
Attacks that exploit this kind of access
create_flowchart. 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_flowchart: 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_flowchart 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_flowchart 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_flowchart. 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_flowchart 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 →