log_usage · Nikhilnt MCP: Risk & Policy

WHAT IT DOES

What log_usage does on Nikhilnt

AI agents use log_usage to create or update resources in Nikhilnt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nikhilnt environment.

WHY IT NEEDS A POLICY

Why log_usage needs a policy

This tool writes usage records (token counts, API call data) to a tracking store. It creates new log entries but does not delete data, execute code, or involve financial transactions. Misuse could result in inaccurate cost tracking but has minimal blast radius.

From the tool's definition "Log a single LLM API call with token counts. Call this after every Claude/GPT/Gemini response."

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_usage Rate-limited

log_usage stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_usage": {
      "limits": [
        {
          "counter": "log_usage_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nikhilnt, so you can run agents against it safely.

FAQ

Questions about log_usage

What does the log_usage tool do? +

Log a single LLM API call with token counts. Call this after every Claude/GPT/Gemini response. It is categorised as a Write tool in the Nikhilnt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_usage? +

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

What risk level is log_usage? +

log_usage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit log_usage? +

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

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

log_usage is provided by the Nikhilnt MCP server (nikhilnt1234/tokenburnrate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.