检查与 StarUML API Server 的连接状态。
AI agents call check_staruml_connection to retrieve information from StarUML MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a diagnostic check of the connection to the StarUML API server. It retrieves and reports connection status without creating, modifying, deleting, executing code, or incurring financial obligations. It is a read-only operation that queries the state of a remote service. The blast radius of misuse is minimal—an agent cannot cause harm by checking a connection status.
From the tool's definition Tool name 'check_staruml_connection' and description '检查与 StarUML API Server 的连接状态' (Check connection status with StarUML API Server) indicates a query/status check operation with no side effects.
Attacks that exploit this kind of access
检查与 StarUML API Server 的连接状态。. It is categorised as a Read tool in the StarUML MCP Server MCP Server, which means it retrieves data without modifying state.
Register the StarUML MCP Server MCP server in PolicyLayer and add a rule for check_staruml_connection: 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.
check_staruml_connection is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_staruml_connection 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 check_staruml_connection. 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.
check_staruml_connection 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 →