get_pagerank
File importance ranking via PageRank on the import graph. Shows most central/important files. Use to identify architecturally critical files. For combined health metrics use get_project_health instead. By default markdown files (.md/.mdx/.markdown/.qmd) are excluded — their cross-link patterns do...
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-pagerank.md
What get_pagerank does on Trace
AI agents call get_pagerank to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_pagerank is rated Low
get_pagerank performs a read-only analysis operation that calculates and returns PageRank metrics on an existing import graph. It retrieves and ranks data without creating, modifying, deleting, executing code, or triggering external operations. The tool explicitly compares itself to get_project_health (a sibling tool for 'combined health metrics'), positioning itself as a pure analysis/query tool.
From the tool's definition Tool description states it 'Shows most central/important files' and 'Use to identify architecturally critical files' — functions as a query/analysis operation on the dependency graph with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_pagerank safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_pagerank, this is the rule to start with:
get_pagerank 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 Trace, apply this rule, and every get_pagerank call is checked against it from then on.
Questions about get_pagerank
File importance ranking via PageRank on the import graph. Shows most central/important files. Use to identify architecturally critical files. For combined health metrics use get_project_health instead. By default markdown files (.md/.mdx/.markdown/.qmd) are excluded — their cross-link patterns dominate the graph and bury real code. Pass. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for get_pagerank: 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 Trace. Nothing to install.
get_pagerank 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 get_pagerank 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 get_pagerank. 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.
get_pagerank is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trace, and thousands of servers like it.
This server
Across the catalogue