graph_analyze
Analyze a graph: count nodes, edges, connected components, density, degrees, and detect self-loops.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/graph-analyze.md
What graph_analyze does on UnClick
AI agents call graph_analyze to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
edges | array | Yes | Array of edges |
directed | boolean | — | Whether the graph is directed (default true) |
Parameters from the server's own tool schema.
Why graph_analyze is rated Low
The tool performs graph analysis and data retrieval operations only. It counts and measures properties of an existing graph structure without creating, modifying, or deleting any data. No side effects, code execution, or destructive operations are involved. This is a straightforward Read category tool with minimal risk if misused.
From the tool's definition Tool description states 'Analyze a graph: count nodes, edges, connected components, density, degrees, and detect self-loops.' These are all read-only analytical operations that retrieve statistics and properties from graph data without modifying, deleting, or…
Attacks that exploit this kind of access
The rule that runs graph_analyze safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For graph_analyze, this is the rule to start with:
graph_analyze is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every graph_analyze call is checked against it from then on.
Questions about graph_analyze
Analyze a graph: count nodes, edges, connected components, density, degrees, and detect self-loops. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
graph_analyze accepts 2 parameters: edges, directed. Required: edges. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for graph_analyze: 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 UnClick. Nothing to install.
graph_analyze 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 graph_analyze 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 graph_analyze. 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.
graph_analyze is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue