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.

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Critical RISK CLASS

Category Destructive

Parameters 11 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/collaborator-delete-collaborator-remote-system-configuration.md

WHAT IT DOES

What collaborator_delete_collaborator_remote_system_configuration does on SmartBear MCP

AI agents call collaborator_delete_collaborator_remote_system_configuration 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
`id`	object	Yes	ID of the remote system Configuration to delete.

Parameters from the server's own tool schema.

RISK

Why collaborator_delete_collaborator_remote_system_configuration is rated Critical

This tool irreversibly removes a remote system configuration. Deletion operations cannot be undone and represent a permanent loss of data/configuration. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because misconfiguration or unauthorized deletion could disrupt system integrations and require significant recovery effort.

From the tool's definition Tool name contains 'delete' and description states 'Deletes a remote system configuration in Collaborator by its ID.' The action is irreversible.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs collaborator_delete_collaborator_remote_system_configuration 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 collaborator_delete_collaborator_remote_system_configuration, this is the rule to start with:

collaborator_delete_collaborator_remote_system_configuration Hidden

collaborator_delete_collaborator_remote_system_configuration is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "collaborator_delete_collaborator_remote_system_configuration"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every collaborator_delete_collaborator_remote_system_configuration call is checked against it from then on.

FAQ

Questions about collaborator_delete_collaborator_remote_system_configuration

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.

What parameters does collaborator_delete_collaborator_remote_system_configuration accept? +

collaborator_delete_collaborator_remote_system_configuration accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on collaborator_delete_collaborator_remote_system_configuration? +

Register the SmartBear MCP server in PolicyLayer and add a rule for collaborator_delete_collaborator_remote_system_configuration: 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.

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 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.

How do I block collaborator_delete_collaborator_remote_system_configuration completely? +

Set action: deny in the PolicyLayer 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 server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →