Given a text, splits it into segments or counts tokens.
AI agents call segment to retrieve information from Jina AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs text analysis and tokenization, which are purely informational operations. It retrieves or derives information from input text without creating, modifying, or deleting data, and does not execute code or trigger external operations. It clearly falls under the Read category with low severity since misuse would at worst produce unwanted text segmentation output with no blast radius.
From the tool's definition Tool description states it 'splits it into segments or counts tokens' - both are read-only operations that analyze text without modifying, deleting, or executing external code. No side effects or state changes.
Attacks that exploit this kind of access
Given a text, splits it into segments or counts tokens. It is categorised as a Read tool in the Jina AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jina AI MCP Server MCP server in PolicyLayer and add a rule for segment: 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 Jina AI MCP Server. Nothing to install.
segment 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 segment 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 segment. 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.
segment is provided by the Jina AI MCP Server MCP server (zk-armor/mcp-jina-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →