count_drivers
AI agents call count_drivers to retrieve information from FleetMind MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Count operations are queries that retrieve aggregated data without modification, deletion, or external execution. This is a classic Read operation. Severity is low as it merely returns a numeric count of drivers with no blast radius for misuse.
From the tool's definition Tool name 'count_drivers' indicates a counting/query operation. Sibling tools like 'count_orders' confirm this is a read-only pattern on the FleetMind server. The empty description provides no contradictory evidence.
Attacks that exploit this kind of access
count_drivers. It is categorised as a Read tool in the FleetMind MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FleetMind MCP Server MCP server in PolicyLayer and add a rule for count_drivers: 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 FleetMind MCP Server. Nothing to install.
count_drivers 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_drivers 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_drivers. 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_drivers is provided by the FleetMind MCP Server MCP server (mashrur-rahman-fahim/fleetmind-mcp). 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 →