This record as markdown: /tools/io-github-kivanccakmak-yaver/android-lint.md
What android_lint does on Yaver
AI agents invoke android_lint 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why android_lint is rated High
This tool executes an external linting tool (Android lint) as part of a build/analysis pipeline. While linting itself is typically non-destructive, it is an Execute action that triggers a subprocess or external operation whose behavior depends on the codebase being checked.
From the tool's definition Tool name 'android_lint' combined with description 'Run Android lint checks' indicates execution of a linting process on Android code. The verb 'Run' explicitly signals code execution.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs android_lint 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 android_lint, this is the rule to start with:
android_lint 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 android_lint call is checked against it from then on.
Questions about android_lint
Run Android lint checks. 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.
android_lint accepts 1 parameter: 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 android_lint: 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.
android_lint 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 android_lint 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 android_lint. 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.
android_lint 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