deleteTeam
Delete a team. Cascades: team members and team-granted resource permissions are removed automatically. Destructive; rate limit 5/min.
This record as markdown: /tools/io-stablebaseline-sb/deleteteam.md
What deleteTeam does on Stable Baseline
AI agents call deleteTeam to permanently remove resources in Stable Baseline, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
team_id | string | Yes |
Parameters from the server's own tool schema.
Why deleteTeam is rated Critical
The tool permanently deletes a team and cascades deletion of team members and resource permissions. This is an irreversible action with broad blast radius affecting multiple entities (team, members, permissions). It falls under Destructive rather than Write because the deletion cannot be undone.
From the tool's definition 'Delete a team. Cascades: team members and team-granted resource permissions are removed automatically.' – explicitly destructive operation that irreversibly removes a team and associated permissions.
Attacks that exploit this kind of access
The rule that runs deleteTeam 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 deleteTeam, this is the rule to start with:
deleteTeam is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every deleteTeam call is checked against it from then on.
Questions about deleteTeam
Delete a team. Cascades: team members and team-granted resource permissions are removed automatically. Destructive; rate limit 5/min. It is categorised as a Destructive tool in the Stable Baseline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteTeam accepts 1 parameter: team_id. Required: team_id. 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 deleteTeam: 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.
deleteTeam is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteTeam 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 deleteTeam. 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.
deleteTeam 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.
Across the catalogue