getDatabaseGuide
How to use the database tools, one topic at a time: filters and operators, totals and analytics, formulas, changing or deleting every row that matches, joins, copying, field types and type changes, tables and views, importing, limits, worked examples and refusals. With no topic it lists the topic...
This record as markdown: /tools/io-stablebaseline-sb/getdatabaseguide.md
What getDatabaseGuide does on Stable Baseline
AI agents call getDatabaseGuide to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
topic | string | — | One topic. Leave out for the list of topics. |
detail | string | — | short (the default) or full. |
section | string | — | One section of the topic, as the list names it. |
Parameters from the server's own tool schema.
Why getDatabaseGuide is rated Low
Even though getDatabaseGuide only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs getDatabaseGuide safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getDatabaseGuide, this is the rule to start with:
getDatabaseGuide is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every getDatabaseGuide call is checked against it from then on.
Questions about getDatabaseGuide
How to use the database tools, one topic at a time: filters and operators, totals and analytics, formulas, changing or deleting every row that matches, joins, copying, field types and type changes, tables and views, importing, limits, worked examples and refusals. With no topic it lists the topics and their sections; pass topic (and section) for one, and detail "full" for more of it. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getDatabaseGuide accepts 3 parameters: topic, detail, section. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for getDatabaseGuide: 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 Stable Baseline. Nothing to install.
getDatabaseGuide 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 getDatabaseGuide 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 getDatabaseGuide. 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.
getDatabaseGuide is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue