list_segmentation_models

List the segmentation models currently loaded on this node.

SERVERTenzro Ledger MCP SOURCEhttps://canton-mcp.tenzro.network/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/network-tenzro-tenzro/list-segmentation-models.md

WHAT IT DOES

What list_segmentation_models does on Tenzro Ledger MCP

AI agents call list_segmentation_models to retrieve information from Tenzro Ledger MCP 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_segmentation_models is rated Low

This tool only queries and returns information about loaded segmentation models. It performs no modifications, deletions, code execution, or financial operations. It is a straightforward read operation with minimal security impact even if invoked by an AI agent without restriction.

From the tool's definition Tool name is 'list_segmentation_models' and description states it 'List[s] the segmentation models currently loaded on this node' — a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_segmentation_models safely

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

list_segmentation_models Allowed

list_segmentation_models 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_segmentation_models": {}
  }
}

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

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

FAQ

Questions about list_segmentation_models

What does the list_segmentation_models tool do? +

List the segmentation models currently loaded on this node. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_segmentation_models? +

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

What risk level is list_segmentation_models? +

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

Can I rate-limit list_segmentation_models? +

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

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

list_segmentation_models is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tenzro Ledger, and thousands of servers like it.

This server

All 360 Tenzro Ledger tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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