Get user count metrics aggregated over time. Track users with accounts, suspended users,
AI agents call get_user_counts to retrieve information from Marqeta DiVA API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries aggregated user count metrics without side effects. It is a simple read operation that returns analytics data. No data is created, modified, deleted, or financial transactions are involved. The low severity reflects minimal risk of misuse—an AI agent querying user metrics poses negligible harm.
From the tool's definition Tool name 'get_user_counts' and description 'Get user count metrics aggregated over time' indicate a retrieval operation.
Attacks that exploit this kind of access
Get user count metrics aggregated over time. Track users with accounts, suspended users,. It is categorised as a Read tool in the Marqeta DiVA API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Marqeta DiVA API MCP Server MCP server in PolicyLayer and add a rule for get_user_counts: 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 Marqeta DiVA API MCP Server. Nothing to install.
get_user_counts 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_user_counts 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_user_counts. 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_user_counts is provided by the Marqeta DiVA API MCP Server MCP server (zvika-finally/marqeta-diva-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 →