projects_reorder
Run projects.reorder through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/projects-reorder.md
What projects_reorder does on Appaloft
AI agents use projects_reorder to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectIds | array | Yes | |
startOffset | integer | — |
Parameters from the server's own tool schema.
Why projects_reorder is rated Medium
Reordering projects is a Write operation: it modifies the sequence/arrangement of existing records but does not delete or create them, and can be reversed. Severity is medium because misuse could disrupt project organization for users, but no data is destroyed.
From the tool's definition 'projects.reorder' — reorders projects, which is a reversible modification of ordering/arrangement data
Attacks that exploit this kind of access
The rule that runs projects_reorder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For projects_reorder, this is the rule to start with:
projects_reorder 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 Appaloft, apply this rule, and every projects_reorder call is checked against it from then on.
Questions about projects_reorder
Run projects.reorder through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
projects_reorder accepts 2 parameters: projectIds, startOffset. Required: projectIds. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for projects_reorder: 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 Appaloft. Nothing to install.
projects_reorder 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 projects_reorder 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 projects_reorder. 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.
projects_reorder is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue