rotate_fleet_invite
Owner-only: rotate a fleet's invite token. Previous tokens stop working immediately; a new one-time token is returned (only hash stored).
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/rotate-fleet-invite.md
What rotate_fleet_invite does on Delx MCP Server
AI agents use rotate_fleet_invite to create or update resources in Delx MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | — | |
fleet_id | string | Yes | |
owner_agent_id | string | — |
Parameters from the server's own tool schema.
Why rotate_fleet_invite is rated Medium
An AI agent can call rotate_fleet_invite faster than any human can review: one bad instruction and it creates or modifies resources in Delx MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs rotate_fleet_invite safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rotate_fleet_invite, this is the rule to start with:
rotate_fleet_invite 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 Delx MCP Server, apply this rule, and every rotate_fleet_invite call is checked against it from then on.
Questions about rotate_fleet_invite
Owner-only: rotate a fleet's invite token. Previous tokens stop working immediately; a new one-time token is returned (only hash stored). It is categorised as a Write tool in the Delx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
rotate_fleet_invite accepts 3 parameters: agent_id, fleet_id, owner_agent_id. Required: fleet_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for rotate_fleet_invite: 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 Delx MCP Server. Nothing to install.
rotate_fleet_invite 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 rotate_fleet_invite 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 rotate_fleet_invite. 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.
rotate_fleet_invite is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue