This record as markdown: /tools/io-github-kivanccakmak-yaver/flutter-doctor.md
What flutter_doctor does on Yaver
AI agents invoke flutter_doctor 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.
Why flutter_doctor is rated High
This tool executes an external command (flutter doctor) to perform diagnostics on the Flutter environment. While the command itself is non-destructive and read-only in practical effect (it only inspects and reports status), the tool definition allows execution of system commands, placing it in the Execute category.
From the tool's definition Tool name 'flutter_doctor' combined with description 'Run flutter doctor to check environment' indicates execution of the flutter doctor command, which is a diagnostic utility that inspects and reports on the local development environment.
Attacks that exploit this kind of access
The rule that runs flutter_doctor 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_doctor, this is the rule to start with:
flutter_doctor 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_doctor call is checked against it from then on.
Questions about flutter_doctor
Run flutter doctor to check environment. 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.
Register the Yaver MCP server in PolicyLayer and add a rule for flutter_doctor: 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_doctor 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_doctor 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_doctor. 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_doctor 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