MCP Server Policy

WEAVIATE MCP POLICY

Enforce policies on every tool call to the Weaviate MCP Server. 2 tools listed, categorised, and ready for rules.

mcp-server-weaviate 1 read 1 write 2 tools total
weaviate database vector-search embeddings

GET STARTED

Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches Weaviate.

terminal

# Download policy scaffold

curl -o weaviate.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/weaviate.yaml

# Run with Intercept

intercept --policy weaviate.yaml -- npx -y @mcp-server-weaviate

Server documentation: https://github.com/weaviate/mcp-server-weaviate

READ TOOLS

1

WRITE TOOLS

1

POLICY YAML

This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.

weaviate.yaml 
version: "1"
description: "Policy for mcp-server-weaviate"
default: "allow"
tools:
    query:
        rules: []
    insert_one:
        rules: []

RELATED POLICIES

ChromaDB 12 tools
databasevector-searchembeddings
MongoDB 36 tools
database
Supabase 32 tools
database
Neon 29 tools
database

FREQUENTLY ASKED QUESTIONS

What tools does the Weaviate MCP server expose?

The Weaviate MCP Server exposes 2 tools across 2 categories: Read, Write. Each tool can be individually controlled with Intercept policies.

How do I enforce policies on Weaviate?

Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the Weaviate MCP server. Every tool call is evaluated against your YAML policy before execution.

Is the Weaviate policy free to use?

Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.

ENFORCE POLICIES ON WEAVIATE

Open source. One binary. Zero dependencies.

VIEW ON GITHUB Browse all policies →