AI agents call export_csv to retrieve information from Nikhilnt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and exports existing usage data in CSV format. It retrieves data without modifying, deleting, or executing anything. The blast radius of misuse is minimal — at worst, it exposes token usage statistics.
From the tool's definition Export usage data as CSV text
Attacks that exploit this kind of access
Export usage data as CSV text. It is categorised as a Read tool in the Nikhilnt MCP Server, which means it retrieves data without modifying state.
Register the Nikhilnt MCP server in PolicyLayer and add a rule for export_csv: 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.
export_csv 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 export_csv 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 export_csv. 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.
export_csv 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.
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 →