collaborator_create_collaborator_remote_system_configuration
Creates a remote system configuration in Collaborator (e.g., Bitbucket, GitHub, etc). Parameters: - token (string) *required*: Remote system token, e.g., BITBUCKET, GITHUB, etc. - title (string) *required*: Remote system title. - config (string) *required*: JSON string containing configuration pa...
This record as markdown: /tools/smartbear-mcp/collaborator-create-collaborator-remote-system-configuration.md
What collaborator_create_collaborator_remote_system_configuration does on SmartBear MCP
AI agents use collaborator_create_collaborator_remote_system_configuration to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Remote system title. |
token | string | Yes | Remote system token, e.g., BITBUCKET, GITHUB, etc. |
config | string | Yes | JSON string containing configuration parameters for the remote system. |
reviewTemplateId | string | — | Optional review template ID used by this remote system. |
Parameters from the server's own tool schema.
Why collaborator_create_collaborator_remote_system_configuration is rated Medium
This tool creates and stores a new remote system configuration (e.g., GitHub, Bitbucket integration) with authentication credentials. While reversible (configurations can typically be deleted), it modifies system state by adding a new integration endpoint that could be used to access external repositories or systems.
From the tool's definition Tool name contains 'create_collaborator' and description states 'Creates a remote system configuration'. Parameters include 'token' (authentication credential), 'title', and 'config' (JSON configuration), indicating persistent creation of a new configuration…
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs collaborator_create_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_create_collaborator_remote_system_configuration, this is the rule to start with:
collaborator_create_collaborator_remote_system_configuration 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 SmartBear MCP, apply this rule, and every collaborator_create_collaborator_remote_system_configuration call is checked against it from then on.
Questions about collaborator_create_collaborator_remote_system_configuration
Creates a remote system configuration in Collaborator (e.g., Bitbucket, GitHub, etc). Parameters: - token (string) *required*: Remote system token, e.g., BITBUCKET, GITHUB, etc. - title (string) *required*: Remote system title. - config (string) *required*: JSON string containing configuration parameters for the remote system. - reviewTemplateId (string): Optional review template ID used by this remote system. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
collaborator_create_collaborator_remote_system_configuration accepts 4 parameters: title, token, config, reviewTemplateId. Required: title, token, config. 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 collaborator_create_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.
collaborator_create_collaborator_remote_system_configuration 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 collaborator_create_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.
Set action: deny in the PolicyLayer policy for collaborator_create_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.
collaborator_create_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.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue