get_tag_segments

List all segments that use a specific tag, paginated

SERVERinstantKOM MCP Server SOURCEinstantkom/mcp-server

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/instantkom-mcp-server/get-tag-segments.md

WHAT IT DOES

What get_tag_segments does on instantKOM MCP Server

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

RISK

Why get_tag_segments is rated Low

This tool performs a read-only operation that retrieves and lists segments associated with a tag. It has no side effects, does not modify or delete data, and does not execute arbitrary operations. It is a straightforward data retrieval function with pagination support, typical of Read category tools.

From the tool's definition Tool name 'get_tag_segments' and description 'List all segments that use a specific tag, paginated' indicate a query/retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_tag_segments safely

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

get_tag_segments Allowed

get_tag_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": {
    "get_tag_segments": {}
  }
}

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

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

FAQ

Questions about get_tag_segments

What does the get_tag_segments tool do? +

List all segments that use a specific tag, paginated. It is categorised as a Read tool in the instantKOM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tag_segments? +

Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for get_tag_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 instantKOM MCP Server. Nothing to install.

What risk level is get_tag_segments? +

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

Can I rate-limit get_tag_segments? +

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

Set action: deny in the PolicyLayer policy for get_tag_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 get_tag_segments? +

get_tag_segments is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on instantKOM MCP Server, and thousands of servers like it.

This server

All 245 instantKOM MCP Server tools →

Across the catalogue

aiva_get_rfm_segments on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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