⚡ AUTO-CONNECT TOOL ⚡ [TRIGGER KEYWORDS] connect to app | find running app | auto-connect | connect to running Flutter | find app | detect app | scan for app | discover app [PRIMARY PURPOSE] Automatically scan for and connect to a running Flutter app (scans VM Service ports 50000-50100). [USE WHE...
Part of the Flutter Skill server.
Free to start. No card required.
AI agents call scan_and_connect to retrieve information from Flutter Skill without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though scan_and_connect only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"scan_and_connect": {}
}
}See the full Flutter Skill policy for all 13 tools.
These attack patterns abuse exactly the kind of access scan_and_connect gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
⚡ AUTO-CONNECT TOOL ⚡ [TRIGGER KEYWORDS] connect to app | find running app | auto-connect | connect to running Flutter | find app | detect app | scan for app | discover app [PRIMARY PURPOSE] Automatically scan for and connect to a running Flutter app (scans VM Service ports 50000-50100). [USE WHEN] • App is already running and you want to connect • Alternative to launch_app when app is already started • Quick reconnection to running app [WORKFLOW] Scans ports, finds first Flutter app, auto-connects. If no app found, use launch_app instead. [AUTO-FIX] If project_path is provided, automatically checks and fixes missing configuration: • Adds flutter_skill dependency to pubspec.yaml if missing • Adds FlutterSkillBinding initialization to main.dart if missing [MULTI-SESSION] Returns a session_id that can be used to target this specific app in subsequent tool calls. Omitting session_id in other tools will use the active session.. It is categorised as a Read tool in the Flutter Skill MCP Server, which means it retrieves data without modifying state.
Register the Flutter Skill MCP server in PolicyLayer and add a rule for scan_and_connect: 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 Flutter Skill. Nothing to install.
scan_and_connect 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 scan_and_connect 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 scan_and_connect. 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.
scan_and_connect is provided by the Flutter Skill MCP server (flutter-skill). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Flutter Skill 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.