Query transactions directly from local SQLite storage using filters.
AI agents call query_local_transactions 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 transaction data from local storage without modifying or deleting it, placing it in the Read category. Severity is high because the tool accesses aggregated financial data including transactions, settlements, and chargebacks - sensitive information whose unauthorized disclosure could enable fraud detection evasion or financial insight leakage.
From the tool's definition Tool is described as 'Query transactions directly from local SQLite storage using filters' - the verb 'query' and 'retrieve' operations indicate data retrieval without modification.
Attacks that exploit this kind of access
Query transactions directly from local SQLite storage using filters. 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 query_local_transactions: 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.
query_local_transactions 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 query_local_transactions 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 query_local_transactions. 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.
query_local_transactions 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 →