Count rows for multiple filter sets in a single call. Optimized for classification, segmentation, and multi-category analysis. Much faster than multiple filter_and_count calls (loads file once, applies all filters). Use for: data classification into categories, market segmentation, quality contro...
AI agents call filter_and_count_batch to retrieve information from Mcp Excel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
filter_and_count_batch performs atomic read operations that retrieve and aggregate information from Excel files. It applies filters and counts matching rows but does not create, modify, delete, or destroy any data. The tool is optimized for analysis and classification tasks with no side effects beyond returning count results.
From the tool's definition Tool counts rows matching filter sets without modifying data. Description states 'Count rows for multiple filter sets' and explicitly mentions 'without loading raw data into context.' Operations listed (filtering, aggregation, counting) are read-only…
Documented attack patterns abuse exactly the kind of access filter_and_count_batch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Excel, and nothing reaches the server without passing your rules. This is the rule we recommend for filter_and_count_batch:
{
"version": "1",
"default": "deny",
"tools": {
"filter_and_count_batch": {}
}
}filter_and_count_batch 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.
Count rows for multiple filter sets in a single call. Optimized for classification, segmentation, and multi-category analysis. Much faster than multiple filter_and_count calls (loads file once, applies all filters). Use for: data classification into categories, market segmentation, quality control checks, multi-condition validation, inventory classification. EXAMPLES: Classify orders (Pending, Processing, Shipped, Delivered), Segment customers (VIP, Regular, Inactive), Quality checks (Pass, Fail, Rework). It is categorised as a Read tool in the Mcp Excel MCP Server, which means it retrieves data without modifying state.
Register the Mcp Excel MCP server in PolicyLayer and add a rule for filter_and_count_batch: 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 Mcp Excel. Nothing to install.
filter_and_count_batch 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 filter_and_count_batch 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 filter_and_count_batch. 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.
filter_and_count_batch is provided by the Mcp Excel MCP server (jwadow/mcp-excel). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Excel, 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.
25 Mcp Excel tools catalogued and risk-classified — across an index of 43,000+ MCP servers.