util_token_estimate
Estimate token count for text. Uses word/4 heuristic (GPT-family) and char/4 (Claude-family). Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing.
This record as markdown: /tools/delx-delx-mcp/util-token-estimate.md
What util_token_estimate does on Delx MCP Server
AI agents call util_token_estimate to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | — | Text to estimate tokens for |
model | string | — | Optional model hint: gpt-4, claude-3, etc. |
Parameters from the server's own tool schema.
Why util_token_estimate is rated Low
This tool retrieves computational metadata about text (token estimation) without side effects. The mention of 'x402 utility pricing' in the description indicates potential cost tracking, but the tool itself does not move money or create financial obligations—it only estimates tokens. Token estimation is a read-only operation that queries properties of input data.
From the tool's definition Tool description indicates it 'Estimate[s] token count for text' using standard heuristics (word/4, char/4). No modification, deletion, execution, or financial commitment occurs—it only analyzes and returns a count estimate.
Attacks that exploit this kind of access
The rule that runs util_token_estimate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_token_estimate, this is the rule to start with:
util_token_estimate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every util_token_estimate call is checked against it from then on.
Questions about util_token_estimate
Estimate token count for text. Uses word/4 heuristic (GPT-family) and char/4 (Claude-family). Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
util_token_estimate accepts 2 parameters: text, model. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for util_token_estimate: 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 Delx MCP Server. Nothing to install.
util_token_estimate 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 util_token_estimate 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 util_token_estimate. 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.
util_token_estimate is provided by the Delx MCP Server MCP server (delx/delx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue