Get card count metrics aggregated over time. Track cards in circulation, active cards,
AI agents call get_card_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 read-only financial metrics (card counts and status summaries) without any capability to modify data, execute operations, or trigger financial transactions. The aggregated nature of the data and lack of side effects categorizes it as a Read operation with low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_card_counts' and description states 'Get card count metrics aggregated over time. Track cards in circulation, active cards' — purely retrieves aggregated metrics with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get card count metrics aggregated over time. Track cards in circulation, active cards,. 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_card_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_card_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_card_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_card_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_card_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 →