contract-testing_admin_delete_team
Delete a team (admin). Parameters: - teamId (string) *required*: UUID of the team
This record as markdown: /tools/smartbear-mcp/contract-testing-admin-delete-team.md
What contract-testing_admin_delete_team does on SmartBear MCP
AI agents call contract-testing_admin_delete_team to permanently remove resources in SmartBear MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
teamId | string | Yes | UUID of the team |
Parameters from the server's own tool schema.
Why contract-testing_admin_delete_team is rated Critical
This tool permanently deletes a team, which cannot be undone. Deletion of organizational units represents an irreversible destructive action with significant blast radius (loss of team data, configurations, and access). While not financial, it is more severe than Execute or Write operations. Classified as Destructive per the severity hierarchy.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a team (admin)'. The operation irreversibly removes a team and all associated data/configurations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs contract-testing_admin_delete_team safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contract-testing_admin_delete_team, this is the rule to start with:
contract-testing_admin_delete_team 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 SmartBear MCP, apply this rule, and every contract-testing_admin_delete_team call is checked against it from then on.
Questions about contract-testing_admin_delete_team
Delete a team (admin). Parameters: - teamId (string) *required*: UUID of the team. It is categorised as a Destructive tool in the SmartBear MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
contract-testing_admin_delete_team accepts 1 parameter: teamId. Required: teamId. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_admin_delete_team: 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 SmartBear MCP. Nothing to install.
contract-testing_admin_delete_team 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 contract-testing_admin_delete_team 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 contract-testing_admin_delete_team. 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.
contract-testing_admin_delete_team is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
Across the catalogue