page_rank
Compute PageRank scores for nodes in a directed graph.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/page-rank.md
What page_rank does on UnClick
AI agents invoke page_rank to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
edges | array | Yes | Array of directed edges {from, to} |
damping | number | — | Damping factor (default 0.85) |
tolerance | number | — | Convergence tolerance (default 1e-6) |
iterations | number | — | Max iterations (default 100) |
Parameters from the server's own tool schema.
Why page_rank is rated High
This tool executes a graph algorithm (PageRank) over supplied input data. It is not a simple data retrieval (no external data source queried), nor does it write, delete, or move money. It runs a computational process whose output depends on the input graph structure, placing it in the Execute category.
From the tool's definition 'Compute PageRank scores for nodes in a directed graph' — performs a computation/algorithm execution on provided graph data
Attacks that exploit this kind of access
The rule that runs page_rank 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 page_rank, this is the rule to start with:
page_rank stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 page_rank call is checked against it from then on.
Questions about page_rank
Compute PageRank scores for nodes in a directed graph. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
page_rank accepts 4 parameters: edges, damping, tolerance, iterations. 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 page_rank: 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.
page_rank is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the page_rank 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 page_rank. 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.
page_rank 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.
Across the catalogue