AI agents call count_sample_tags to retrieve information from FiftyOne MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only aggregation query on dataset metadata. It retrieves counts of tags across samples but does not create, modify, delete, or execute any operations. The verb 'count' and the aggregation context indicate a passive data retrieval operation with no side effects.
From the tool's definition Tool name is 'count_sample_tags' and description indicates it 'Count[s] how many samples have each tag' — a query operation that retrieves and aggregates tag statistics without modifying data.
Documented attack patterns abuse exactly the kind of access count_sample_tags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FiftyOne MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for count_sample_tags:
{
"version": "1",
"default": "deny",
"tools": {
"count_sample_tags": {}
}
}count_sample_tags 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 how many samples have each tag in a. It is categorised as a Read tool in the FiftyOne MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FiftyOne MCP Server MCP server in PolicyLayer and add a rule for count_sample_tags: 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 FiftyOne MCP Server. Nothing to install.
count_sample_tags 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 count_sample_tags 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 count_sample_tags. 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.
count_sample_tags is provided by the FiftyOne MCP Server MCP server (voxel51/fiftyone-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FiftyOne MCP Server, 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.
47 FiftyOne MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.