This record as markdown: /tools/io-github-kivanccakmak-yaver/flutter-build.md
What flutter_build does on Yaver
AI agents invoke flutter_build to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
platform | string | — | apk, appbundle, ios, web, macos, linux, windows |
directory | string | — |
Parameters from the server's own tool schema.
Why flutter_build is rated High
Flutter builds compile source code into native binaries/APKs/app packages—a form of code execution with side effects (artifact creation, potential network calls during dependency resolution). This is not merely a read (no data retrieval), not a write to user data (reversible), and not destructive in the traditional sense, but it IS an execute operation.
From the tool's definition Tool name 'flutter_build' and description 'Build a Flutter app' indicate execution of a build process, which compiles code and produces artifacts. Building is an external operation whose effects depend on the app configuration and source code.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs flutter_build 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 flutter_build, this is the rule to start with:
flutter_build stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 flutter_build call is checked against it from then on.
Questions about flutter_build
Build a Flutter app. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
flutter_build accepts 2 parameters: platform, directory. 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 flutter_build: 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.
flutter_build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the flutter_build 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 flutter_build. 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.
flutter_build 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.
Across the catalogue