Get ChromaDB and collection information
AI agents call db_info to retrieve information from AI Research Assistant MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries database metadata and collection information, which is a non-destructive retrieval operation. It has no side effects, does not modify data, execute code with variable effects, delete data, or handle financial operations. The blast radius of misuse is minimal—an agent could learn about database structure but cannot alter or manipulate data through this tool alone.
From the tool's definition Tool name 'db_info' and description 'Get ChromaDB and collection information' indicate retrieval of metadata and status information without modification. The verb 'Get' is characteristic of read operations.
Attacks that exploit this kind of access
Get ChromaDB and collection information. It is categorised as a Read tool in the AI Research Assistant MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AI Research Assistant MCP Server MCP server in PolicyLayer and add a rule for db_info: 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 AI Research Assistant MCP Server. Nothing to install.
db_info 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 db_info 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 db_info. 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.
db_info is provided by the AI Research Assistant MCP Server MCP server (sagarkpoojary/sagar-mcp-project). 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 →