Low Risk

search_docs

Search the Supabase documentation using GraphQL. Must be a valid GraphQL query. You should default to calling this even if you think you already know the answer, since the documentation is always being updated. Below is the GraphQL schema for this tool: schema{query:RootQueryType}type Guide imp...

Part of the Supabase Godmode MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call search_docs to retrieve information from Supabase Godmode without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_docs only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

ubiq-supabase-godmode.yaml
tools:
  search_docs:
    rules:
      - action: allow

See the full Supabase Godmode policy for all 29 tools.

Tool Name search_docs
Category Read
Risk Level Low

View all 29 tools →

Agents calling read-class tools like search_docs have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the search_docs tool do? +

Search the Supabase documentation using GraphQL. Must be a valid GraphQL query. You should default to calling this even if you think you already know the answer, since the documentation is always being updated. Below is the GraphQL schema for this tool: schema{query:RootQueryType}type Guide implements SearchResult{title:String href:String content:String subsections:SubsectionCollection}interface SearchResult{title:String href:String content:String}type SubsectionCollection{edges:[SubsectionEdge!]! nodes:[Subsection!]! totalCount:Int!}type SubsectionEdge{node:Subsection!}type Subsection{title:String href:String content:String}type CLICommandReference implements SearchResult{title:String href:String content:String}type ManagementApiReference implements SearchResult{title:String href:String content:String}type ClientLibraryFunctionReference implements SearchResult{title:String href:String content:String language:Language! methodName:String}enum Language{JAVASCRIPT SWIFT DART CSHARP KOTLIN PYTHON}type TroubleshootingGuide implements SearchResult{title:String href:String content:String}type RootQueryType{schema:String! searchDocs(query:String!,limit:Int):SearchResultCollection error(code:String!,service:Service!):Error errors(first:Int after:String last:Int before:String service:Service code:String):ErrorCollection}type SearchResultCollection{edges:[SearchResultEdge!]! nodes:[SearchResult!]! totalCount:Int!}type SearchResultEdge{node:SearchResult!}type Error{code:String! service:Service! httpStatusCode:Int message:String}enum Service{AUTH REALTIME STORAGE}type ErrorCollection{edges:[ErrorEdge!]! nodes:[Error!]! pageInfo:PageInfo! totalCount:Int!}type ErrorEdge{node:Error! cursor:String!}type PageInfo{hasNextPage:Boolean! hasPreviousPage:Boolean! startCursor:String endCursor:String}. It is categorised as a Read tool in the Supabase Godmode MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_docs? +

Add a rule in your Intercept YAML policy under the tools section for search_docs. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Supabase Godmode MCP server.

What risk level is search_docs? +

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

Can I rate-limit search_docs? +

Yes. Add a rate_limit block to the search_docs rule in your Intercept 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 search_docs completely? +

Set action: deny in the Intercept policy for search_docs. 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 search_docs? +

search_docs is provided by the Supabase Godmode MCP server (ubiq/supabase-godmode). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Supabase Godmode

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.