// MCP TOOL REFERENCE

collaborator_delete_collaborator_remote_system_configuration

Deletes a remote system configuration in Collaborator by its ID. **Parameters:** - id (union) *required*: ID of the remote system Configuration to delete.

Single-target operation

Part of the SmartBear MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@smartbear/mcp Destructive

// WHEN AI AGENTS USE THIS TOOL

AI agents may call collaborator_delete_collaborator_remote_system_configuration to permanently remove or destroy resources in SmartBear MCP. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON COLLABORATOR_DELETE_COLLABORATOR_REMOTE_SYSTEM_CONFIGURATION

Without a policy, an AI agent could call collaborator_delete_collaborator_remote_system_configuration in a loop, permanently destroying resources in SmartBear MCP. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

smartbear-mcp.yaml

tools:
  collaborator_delete_collaborator_remote_system_configuration:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full SmartBear MCP policy for all 243 tools.

// DETAILS

Tool Name collaborator_delete_collaborator_remote_system_configuration

Category Destructive

MCP Server SmartBear MCP MCP Server

Risk Level Critical

// MORE SMARTBEAR MCP TOOLS

Destructive contract-testing_admin_delete_role Destructive contract-testing_admin_delete_team Destructive contract-testing_admin_delete_user Destructive contract-testing_admin_remove_role_from_user Destructive contract-testing_admin_remove_user_from_team Destructive contract-testing_admin_reset_roles Destructive contract-testing_delete_all_integrations Destructive contract-testing_delete_branch

View all 243 tools →

// WHAT CAN GO WRONG

Agents calling destructive-class tools like collaborator_delete_collaborator_remote_system_configuration have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete ACR — Agent Composition Records acknowledge_threat AdButler campaign_bulk_delete_catalog_ad_items

// IN CONTEXT OF CRITICAL RISK

collaborator_delete_collaborator_remote_system_configuration is one of the critical-risk operations in SmartBear MCP. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the collaborator_delete_collaborator_remote_system_configuration tool do? +

Deletes a remote system configuration in Collaborator by its ID. **Parameters:** - id (union) *required*: ID of the remote system Configuration to delete.. 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.

How do I enforce a policy on collaborator_delete_collaborator_remote_system_configuration? +

Add a rule in your Intercept YAML policy under the tools section for collaborator_delete_collaborator_remote_system_configuration. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

What risk level is collaborator_delete_collaborator_remote_system_configuration? +

collaborator_delete_collaborator_remote_system_configuration is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit collaborator_delete_collaborator_remote_system_configuration? +

Yes. Add a rate_limit block to the collaborator_delete_collaborator_remote_system_configuration rule in your Intercept 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.

How do I block collaborator_delete_collaborator_remote_system_configuration completely? +

Set action: deny in the Intercept policy for collaborator_delete_collaborator_remote_system_configuration. 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.

What MCP server provides collaborator_delete_collaborator_remote_system_configuration? +

collaborator_delete_collaborator_remote_system_configuration is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

collaborator_delete_collaborator_remote_system_configuration

Let agents act without letting them run wild.