Expand Database Queries to Whitelist StoredProcedures

[sitefinitysteve]

Right now boost sees my SP, tries to call it, but it throws "Only read-only queries are allowed", this specific stored procedure IS only a Select, no manipulation of the database.

It would be great if I could somehow allow specific items to be called ideally though a wildcard, but I'm fine with specific names.

[pushpak1300]

I don’t think this should be added to Boost. Supporting all different DB features would make it too bloated and hard for maintenance. For cases like this, you can use a database-specific MCP, such as postgres-mcp. That feels like a better fit.

Also you can easily extend Boost Tools to support this specific functionality in your application.

[sitefinitysteve]

Yeah I suppose 100% agree not make db specific sorry, maybe a bad request based on what CC was outputting, but hear me out, maybe its a bug not a feature. I think in the moment I assumed it could call the SP, when in fact it DID, was blocked by a followup on it.

So like I said boost ALREADY called the SP through tinker and got results back to analyze:

laravel-boost - tinker (MCP)(code: "// Let's check what the stored procedure returns
.... other stuff
DB::select('CALL GetContractSectionsWithResolvedContent(?, ?)', [$contractId, $variantId]);

Returned 270 something results it then looked at

But then tanked on this

Let me check if the stored procedure has a depth limitation or if it's missing nested children:


⏺ laravel-boost - database-query (MCP)(query: "WITH RECURSIVE section_hierarchy AS (\n  -- Base case: root sections\n  SELECT s.id, s.parent_id,
                                      s.section_group_id, s.order, 1 as depth\n  FROM sections s \n  WHERE s.parent_id IS NULL\n  AND
                                      s.section_group_id IN (\n    SELECT sg.id FROM section_groups sg WHERE sg.contract_id =
                                      '1b6288ea-f020-4a08-a534-baa641ac7ea3'\n  )\n  \n  UNION ALL\n  \n  -- Recursive case: child sections\n  SELECT
                                       s.id, s.parent_id, s.section_group_id, s.order, sh.depth + 1\n  FROM sections s\n  INNER JOIN
                                      section_hierarchy sh ON s.parent_id = sh.id\n  WHERE sh.depth < 10  -- Prevent infinite recursion\n)\nSELECT \n
                                        depth,\n  COUNT(*) as section_count\nFROM section_hierarchy \nGROUP BY depth\nORDER BY depth")
  ⎿  Error: Only read-only queries are allowed (SELECT, SHOW, EXPLAIN, DESCRIBE, DESC, WITH … SELECT).

So is that a bug then with the next tool call into dbquery?