Medium Risk

create_tester_group

Creates a tester group for a Release Management connected app. Tester groups can be used to distribute installable artifacts to testers automatically. When a new installable artifact is available, the tester groups can either automatically or manually be notified via email. The notification email...

Risk signalsAdmin/system-level operation

Part of the Bitrise server.

create_tester_group can modify Bitrise data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE BITRISE →

Free to start. No card required.

AI agents use create_tester_group to create or modify resources in Bitrise. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call create_tester_group repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Bitrise.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_tester_group": {
      "limits": [
        {
          "counter": "create_tester_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Bitrise policy for all 81 tools.

Get this rule live on your own Bitrise server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY BITRISE →

View all 81 tools →

These attack patterns abuse exactly the kind of access create_tester_group gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so create_tester_group only ever does what you allow.

SECURE BITRISE →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the create_tester_group tool do? +

Creates a tester group for a Release Management connected app. Tester groups can be used to distribute installable artifacts to testers automatically. When a new installable artifact is available, the tester groups can either automatically or manually be notified via email. The notification email will contain a link to the installable artifact page for the artifact within Bitrise Release Management. A Release Management connected app can have multiple tester groups. Project team members of the connected app can be selected to be testers and added to the tester group. This endpoint has an elevated access level requirement. Only the owner of the related Bitrise Workspace, a workspace manager or the related project's admin can manage tester groups.. It is categorised as a Write tool in the Bitrise MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_tester_group? +

Register the Bitrise MCP server in PolicyLayer and add a rule for create_tester_group: 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 Bitrise. Nothing to install.

What risk level is create_tester_group? +

create_tester_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_tester_group? +

Yes. Add a rate_limit block to the create_tester_group 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 create_tester_group completely? +

Set action: deny in the PolicyLayer policy for create_tester_group. 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 create_tester_group? +

create_tester_group is provided by the Bitrise MCP server (https://mcp.bitrise.io/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bitrise tool call.

Deterministic rules across all 81 Bitrise tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.