libi.list_track_segments

List a track

SERVERLibi SOURCENagellabs/libi

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/libi/libi.list-track-segments.md

WHAT IT DOES

What libi.list_track_segments does on Libi

AI agents call libi.list_track_segments to retrieve information from Libi without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why libi.list_track_segments is rated Low

Tool queries track segments without side effects or data changes.

From the tool's definition List a track — retrieves data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs libi.list_track_segments safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Libi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For libi.list_track_segments, this is the rule to start with:

libi.list_track_segments Allowed

libi.list_track_segments 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": {
    "libi.list_track_segments": {}
  }
}

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

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

FAQ

Questions about libi.list_track_segments

What does the libi.list_track_segments tool do? +

List a track. It is categorised as a Read tool in the Libi MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on libi.list_track_segments? +

Register the Libi MCP server in PolicyLayer and add a rule for libi.list_track_segments: 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 Libi. Nothing to install.

What risk level is libi.list_track_segments? +

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

Can I rate-limit libi.list_track_segments? +

Yes. Add a rate_limit block to the libi.list_track_segments 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 libi.list_track_segments completely? +

Set action: deny in the PolicyLayer policy for libi.list_track_segments. 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 libi.list_track_segments? +

libi.list_track_segments is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Libi, and thousands of servers like it.

This server

All 215 Libi tools →

Across the catalogue

aiva_get_rfm_segments on AIVA MCP Server → The MCP Attack Database →

Guides

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