list_pins

List all active ranking pins with weight, scope, target, expiry, and creator. Use to inspect what is currently boosted/demoted in PageRank-driven ranking. Read-only. Returns JSON: { pins: [{ scope, target_id, weight, expires_at, created_by, created_at }], total, cap }.

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/list-pins.md

WHAT IT DOES

What list_pins does on Trace

AI agents call list_pins 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.

RISK

Why list_pins is rated Low

This tool queries and returns metadata about active ranking pins (scope, target_id, weight, expiry, creator). It has no side effects, cannot modify data, and does not execute code or trigger external operations. It is purely informational retrieval, making it a standard Read operation with low blast radius if misused.

From the tool's definition The tool description explicitly states 'Read-only' and uses verbs like 'List' and 'inspect'. It retrieves PageRank ranking pin configurations without modifying or executing any operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_pins 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 list_pins, this is the rule to start with:

list_pins Allowed

list_pins is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_pins": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every list_pins call is checked against it from then on.

FAQ

Questions about list_pins

What does the list_pins tool do? +

How do I enforce a policy on list_pins? +

Register the Trace MCP server in PolicyLayer and add a rule for list_pins: 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.

What risk level is list_pins? +

list_pins is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_pins? +

Yes. Add a rate_limit block to the list_pins 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.

How do I block list_pins completely? +

Set action: deny in the PolicyLayer policy for list_pins. 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.

What MCP server provides list_pins? +

list_pins 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.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →