Get card detail data. Includes user tokens, card state, active status, and UAI.
AI agents call get_cards 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 sensitive financial and user data (card details, user tokens, card state, active status, and UAI identifiers) but does not modify, delete, or execute operations. It is clearly a Read operation.
From the tool's definition Tool name is 'get_cards' and description states 'Get card detail data. Includes user tokens, card state, active status, and UAI.' The verb 'Get' and phrase 'card detail data' indicate retrieval/querying with no side effects.
Attacks that exploit this kind of access
Get card detail data. Includes user tokens, card state, active status, and UAI. 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_cards: 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_cards 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_cards 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_cards. 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_cards 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 →