Get load transaction data. Includes load amounts and transaction details.
AI agents call get_loads 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 financial transaction data (loads, amounts, details) from the Marqeta DiVA API. While it accesses sensitive financial information that could inform fraud or unauthorized activity if misused by an AI agent, the tool itself performs no destructive, executable, or financial action—it only queries and returns data.
From the tool's definition Tool name 'get_loads' and description 'Get load transaction data. Includes load amounts and transaction details.' indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Get load transaction data. Includes load amounts and transaction details. 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_loads: 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_loads 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_loads 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_loads. 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_loads 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 →