rebuildPlatformCatalogEmbeddings
Maintenance (requires write). Refreshes the search index over every platform catalogue (MCP tools, whiteboard stencils, architecture icons, infographic templates, whiteboard design components and design skills), so that search by meaning in searchTools, listWhiteboardStencils, listArchitectureIco...
This record as markdown: /tools/io-stablebaseline-sb/rebuildplatformcatalogembeddings.md
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 catalogues to sync. Defaults to all six (tool, stencil, icon, infographic_template, whiteboard_component, skill). |
Parameters from the server's own tool schema.
Why rebuildPlatformCatalogEmbeddings is rated Medium
An AI agent can call rebuildPlatformCatalogEmbeddings faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
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 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.
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.
Questions about rebuildPlatformCatalogEmbeddings
Maintenance (requires write). Refreshes the search index over every platform catalogue (MCP tools, whiteboard stencils, architecture icons, infographic templates, whiteboard design components and design skills), so that search by meaning in searchTools, listWhiteboardStencils, listArchitectureIcons and the design skill and component browsers stays current. Incremental: it scans every catalogue and re-indexes ONLY the entries that changed (a cheap no-op when nothing changed). This normally runs automatically every hour, so manual calls are rarely needed; use it to force an immediate refresh after changing any catalogue. Handles up to ~120 changed entries 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.
rebuildPlatformCatalogEmbeddings accepts 1 parameter: types. 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 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.
rebuildPlatformCatalogEmbeddings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue