AI agents call get_value_counts to retrieve information from CSV Editor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a statistical query on CSV data (counting distinct values and their frequencies), which is a read-only operation with no side effects. It retrieves information without altering the underlying dataset. The low severity reflects minimal risk even if misused by an AI agent, as it only returns aggregate statistics.
From the tool's definition Tool name 'get_value_counts' and description 'Get value counts for a column' indicate a data retrieval operation that queries and returns frequency counts for values in a CSV column. No modification, deletion, or execution of arbitrary code is involved.
Documented attack patterns abuse exactly the kind of access get_value_counts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CSV Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for get_value_counts:
{
"version": "1",
"default": "deny",
"tools": {
"get_value_counts": {}
}
}get_value_counts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get value counts for a column. It is categorised as a Read tool in the CSV Editor MCP Server, which means it retrieves data without modifying state.
Register the CSV Editor MCP server in PolicyLayer and add a rule for get_value_counts: 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 CSV Editor. Nothing to install.
get_value_counts 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 get_value_counts 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 get_value_counts. 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.
get_value_counts is provided by the CSV Editor MCP server (santoshray02/csv-editor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CSV Editor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 CSV Editor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.