get_index_stats

Get comprehensive statistics about local storage (SQLite + ChromaDB).

Server Marqeta DiVA API MCP Server zvika-finally/marqeta-diva-mcp
Category Read
Risk class Low
Parameters 00 required

What get_index_stats does on Marqeta DiVA API MCP Server

AI agents call get_index_stats 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.

Why get_index_stats needs a policy

This tool queries and retrieves statistics from internal storage systems. It performs no data modification, code execution, deletion, or financial operations. The blast radius is minimal—an AI agent invoking this tool could only gain information about local storage configuration and state, with no side effects on business operations or data integrity.

From the tool's definition Tool name 'get_index_stats' and description 'Get comprehensive statistics about local storage (SQLite + ChromaDB)' indicate a read-only operation that retrieves metadata and statistics without modifying, executing external operations, or causing financial…

Questions about get_index_stats

What does the get_index_stats tool do? +

Get comprehensive statistics about local storage (SQLite + ChromaDB). It is categorised as a Read tool in the Marqeta DiVA API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_index_stats? +

Register the Marqeta DiVA API MCP Server MCP server in PolicyLayer and add a rule for get_index_stats: 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.

What risk level is get_index_stats? +

get_index_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_index_stats? +

Yes. Add a rate_limit block to the get_index_stats 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.

How do I block get_index_stats completely? +

Set action: deny in the PolicyLayer policy for get_index_stats. 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.

What MCP server provides get_index_stats? +

get_index_stats 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.