rebuildPlatformCatalogEmbeddings

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Medium RISK CLASS

Category Write

Parameters 10 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/rebuildplatformcatalogembeddings.md

WHAT IT DOES

What rebuildPlatformCatalogEmbeddings does on Stable Baseline

AI agents use rebuildPlatformCatalogEmbeddings to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.

Parameter	Type	Required	Description
`types`	array	—	Which catalogs to sync. Defaults to all six (tool, stencil, icon, infographic_template, whiteboard_component, skill).

Parameters from the server's own tool schema.

RISK

Why rebuildPlatformCatalogEmbeddings is rated Medium

This tool modifies data (vector embeddings in platform_catalog_embeddings table) across multiple platform catalogs. While it is incremental and non-destructive, it is a write operation that updates system state affecting search functionality for the entire platform.

From the tool's definition Internal maintenance (requires write). Syncs gte-small (384-dim) vector embeddings for every platform catalog into platform_catalog_embeddings. Scans every catalog, diffs by content hash, and re-embeds ONLY changed rows.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rebuildPlatformCatalogEmbeddings 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 rebuildPlatformCatalogEmbeddings, this is the rule to start with:

rebuildPlatformCatalogEmbeddings Rate-limited

rebuildPlatformCatalogEmbeddings stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rebuildPlatformCatalogEmbeddings": {
      "limits": [
        {
          "counter": "rebuildplatformcatalogembeddings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every rebuildPlatformCatalogEmbeddings call is checked against it from then on.

FAQ

Questions about rebuildPlatformCatalogEmbeddings

What does the rebuildPlatformCatalogEmbeddings tool do? +

Internal maintenance (requires write). Syncs gte-small (384-dim) vector embeddings for every platform catalog (MCP tools, whiteboard stencils, architecture icons, infographic templates, whiteboard design components, and open-design skills) into platform_catalog_embeddings, so the semantic search behind searchTools, listWhiteboardStencils, listArchitectureIcons, and the design-skill / component browsers stays current. Incremental: scans every catalog, diffs by content hash, and re-embeds ONLY changed rows (cheap no-op when nothing changed). This normally runs automatically every hour (the platform-catalog-sync cron), so manual calls are rarely needed; use it to force an immediate sync after changing any catalog. Embeds up to ~120 changed rows per call; if more changed, call again until allDone is true. Not part of normal authoring flows. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does rebuildPlatformCatalogEmbeddings accept? +

rebuildPlatformCatalogEmbeddings accepts 1 parameter: types. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on rebuildPlatformCatalogEmbeddings? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for rebuildPlatformCatalogEmbeddings: 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.

What risk level is rebuildPlatformCatalogEmbeddings? +

rebuildPlatformCatalogEmbeddings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rebuildPlatformCatalogEmbeddings? +

Yes. Add a rate_limit block to the rebuildPlatformCatalogEmbeddings 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.

How do I block rebuildPlatformCatalogEmbeddings completely? +

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

rebuildPlatformCatalogEmbeddings 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.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 196 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →