count_accounts_by_criteria
Count accounts by various criteria (platform, safe, management status).
This record as markdown: /tools/aaearon-mcp-privilege-cloud/count-accounts-by-criteria.md
What count_accounts_by_criteria does on CyberArk Privilege Cloud MCP Server
AI agents call count_accounts_by_criteria to retrieve information from CyberArk Privilege Cloud MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why count_accounts_by_criteria is rated Low
The tool performs a counting and querying operation on account metadata (filtering by platform, safe, management status). This is a non-destructive read operation with no side effects. It returns aggregate statistics only. The blast radius of misuse is minimal—an attacker could enumerate accounts or discover organizational structure, but cannot modify, delete, or move resources.
From the tool's definition Tool name is 'count_accounts_by_criteria' and description states it 'Count accounts by various criteria' — this is a query/aggregation operation that retrieves data without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs count_accounts_by_criteria safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CyberArk Privilege Cloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For count_accounts_by_criteria, this is the rule to start with:
count_accounts_by_criteria is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CyberArk Privilege Cloud MCP Server, apply this rule, and every count_accounts_by_criteria call is checked against it from then on.
Questions about count_accounts_by_criteria
Count accounts by various criteria (platform, safe, management status). It is categorised as a Read tool in the CyberArk Privilege Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CyberArk Privilege Cloud MCP Server MCP server in PolicyLayer and add a rule for count_accounts_by_criteria: 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 CyberArk Privilege Cloud MCP Server. Nothing to install.
count_accounts_by_criteria 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_accounts_by_criteria 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_accounts_by_criteria. 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_accounts_by_criteria is provided by the CyberArk Privilege Cloud MCP Server MCP server (aaearon/mcp-privilege-cloud). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CyberArk Privilege Cloud MCP Server, and thousands of servers like it.
Across the catalogue