reorderImprovementCategories
Reorder improvement categories by setting sort_order values.
This record as markdown: /tools/io-stablebaseline-sb/reorderimprovementcategories.md
What reorderImprovementCategories does on Stable Baseline
AI agents use reorderImprovementCategories 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 |
|---|---|---|---|
items | array | Yes | Array of {categoryId, sortOrder}. |
Parameters from the server's own tool schema.
Why reorderImprovementCategories is rated Medium
This tool modifies data (sort_order values) in a reversible manner without deleting or destroying data, placing it in the Write category. The severity is medium because reordering could affect UI/UX presentation and workflow priority, but the changes are easily reversible by reordering again. Confidence is high because the description clearly indicates a data modification operation.
From the tool's definition Tool description explicitly states 'Reorder improvement categories by setting sort_order values' — a modification operation that updates existing records.
Attacks that exploit this kind of access
The rule that runs reorderImprovementCategories 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 reorderImprovementCategories, this is the rule to start with:
reorderImprovementCategories 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 reorderImprovementCategories call is checked against it from then on.
Questions about reorderImprovementCategories
Reorder improvement categories by setting sort_order values. 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.
reorderImprovementCategories accepts 1 parameter: items. Required: items. 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 reorderImprovementCategories: 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.
reorderImprovementCategories 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 reorderImprovementCategories 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 reorderImprovementCategories. 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.
reorderImprovementCategories 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