Get vector database configuration
AI agents call get_vector_database_info to retrieve information from AnythingLLM 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 configuration information about a vector database. The verb 'get' and lack of any modifying language ('delete', 'update', 'create', 'execute') clearly indicate a read-only query operation. Accessing configuration data poses minimal risk compared to write, execute, or destructive operations—it simply exposes existing metadata without enabling changes to systems or data.
From the tool's definition Tool name 'get_vector_database_info' and description 'Get vector database configuration' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_vector_database_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AnythingLLM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_vector_database_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_vector_database_info": {}
}
}get_vector_database_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get vector database configuration. It is categorised as a Read tool in the AnythingLLM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AnythingLLM MCP Server MCP server in PolicyLayer and add a rule for get_vector_database_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 AnythingLLM MCP Server. Nothing to install.
get_vector_database_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 get_vector_database_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 get_vector_database_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.
get_vector_database_info is provided by the AnythingLLM MCP Server MCP server (raqueljezweb/anythingllm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AnythingLLM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 AnythingLLM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.