This record as markdown: /tools/io-github-kivanccakmak-yaver/testflight-builds.md
What testflight_builds does on Yaver
AI agents call testflight_builds to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
bundle_id | string | Yes |
Parameters from the server's own tool schema.
Why testflight_builds is rated Low
This tool retrieves and lists existing TestFlight build information. It performs a read-only query against Apple's TestFlight service without modifying, creating, deleting, or executing any code. The blast radius of misuse is minimal—an attacker gains only visibility into build metadata, not the ability to alter builds, delete them, or trigger deployments.
From the tool's definition Tool name 'testflight_builds' and description 'List TestFlight builds for an app' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs testflight_builds safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For testflight_builds, this is the rule to start with:
testflight_builds is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every testflight_builds call is checked against it from then on.
Questions about testflight_builds
List TestFlight builds for an app. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
testflight_builds accepts 1 parameter: bundle_id. Required: bundle_id. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for testflight_builds: 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 Yaver. Nothing to install.
testflight_builds is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the testflight_builds 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 testflight_builds. 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.
testflight_builds is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue