Get the current status of the knowledge base vector store.
AI agents call get_vectorstore_status to retrieve information from Combined 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 metadata about a vector store's operational state. It performs no mutations, does not execute code or queries, does not delete data, and has no financial implications. The operation has minimal blast radius—at worst, an AI agent gains visibility into store status, which could inform decisions but causes no direct harm. This is a straightforward Read classification.
From the tool's definition Tool name 'get_vectorstore_status' and description 'Get the current status' indicate a read-only query operation that retrieves status information without modifying or executing anything.
Attacks that exploit this kind of access
Get the current status of the knowledge base vector store. It is categorised as a Read tool in the Combined MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Combined MCP Server MCP server in PolicyLayer and add a rule for get_vectorstore_status: 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 Combined MCP Server. Nothing to install.
get_vectorstore_status 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_vectorstore_status 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_vectorstore_status. 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_vectorstore_status is provided by the Combined MCP Server MCP server (manish6007/mcp_servers). 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 →