Clear all transactions from the vector index.
AI agents call clear_index to permanently remove resources in Marqeta DiVA API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes all transaction data from the vector index without the ability to undo the action. While the underlying transaction records in the primary database may persist, the destruction of the entire indexed dataset represents a destructive operation that cannot be reversed and would severely impact the availability and usability of the DiVA API's semantic search and RAG features.
From the tool's definition 'Clear all transactions from the vector index' - the verb 'clear' with scope 'all transactions' indicates irreversible deletion of indexed data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all transactions from the vector index. It is categorised as a Destructive tool in the Marqeta DiVA API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Marqeta DiVA API MCP Server MCP server in PolicyLayer and add a rule for clear_index: 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.
clear_index is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_index 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 clear_index. 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.
clear_index 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 →