Low Risk

turncost_calculate

Calculate Turn Cost governance metrics for a time period. Returns frame count, estimated tokens, and prompt count to help measure coordination overhead.

Part of the Lex MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call turncost_calculate to retrieve information from Lex without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though turncost_calculate only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

lex.yaml
tools:
  turncost_calculate:
    rules:
      - action: allow

See the full Lex policy for all 14 tools.

Tool Name turncost_calculate
Category Read
MCP Server Lex MCP Server
Risk Level Low

View all 14 tools →

What does the turncost_calculate tool do? +

Calculate Turn Cost governance metrics for a time period. Returns frame count, estimated tokens, and prompt count to help measure coordination overhead.. It is categorised as a Read tool in the Lex MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on turncost_calculate? +

Add a rule in your Intercept YAML policy under the tools section for turncost_calculate. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Lex MCP server.

What risk level is turncost_calculate? +

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

Can I rate-limit turncost_calculate? +

Yes. Add a rate_limit block to the turncost_calculate rule in your Intercept 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 turncost_calculate completely? +

Set action: deny in the Intercept policy for turncost_calculate. 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 turncost_calculate? +

turncost_calculate is provided by the Lex MCP server (@smartergpt/lex-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Lex

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.