Total count of active (non-deleted) customers, optionally filtered by country code (US, UK, DE, etc.).
AI agents call get_customer_count to retrieve information from Semantic BI MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a metric (customer count) with no capability to modify, delete, or execute operations. It is a read-only query of aggregated business data. Severity is low because the information is non-sensitive customer count metrics that would typically be accessible to authorized analysts, and misuse cannot damage systems or data.
From the tool's definition Tool description: 'Total count of active (non-deleted) customers, optionally filtered by country code'. The verb 'count' and 'get_' prefix indicate data retrieval. The optional filtering parameter does not modify data.
Attacks that exploit this kind of access
Total count of active (non-deleted) customers, optionally filtered by country code (US, UK, DE, etc.). It is categorised as a Read tool in the Semantic BI MCP MCP Server, which means it retrieves data without modifying state.
Register the Semantic BI MCP server in PolicyLayer and add a rule for get_customer_count: 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 Semantic BI MCP. Nothing to install.
get_customer_count 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_customer_count 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_customer_count. 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_customer_count is provided by the Semantic BI MCP server (lovrobubanic/semantic-bi-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 →