Fetches the full text of a single stock Android documentation entry by its knowledge-base URI (kb://...), as returned by search_android_docs. Use this after search_android_docs to read a complete guide or API reference. Requires Google's android CLI on the MCP host's PATH (an optional runtime dep...
AI agents call fetch_android_doc to retrieve information from Sceneview without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
uri | string | Yes | The knowledge-base URI to fetch, e.g. "kb://compose/lists/lazy-column". A bare path with no scheme is tolerated and normalised to kb://. |
Parameters from the server's own tool schema.
This tool retrieves and queries existing Android documentation without modifying, executing code, deleting, or creating side effects. It is a straightforward read operation that returns documentation text based on a knowledge-base URI. The requirement for Google's android CLI is a runtime dependency check, not an execution of arbitrary commands. No data modification, deletion, or financial impact occurs.
From the tool's definition Tool description states 'Fetches the full text of a single stock Android documentation entry' and is used 'after search_android_docs to read a complete guide or API reference.' The verb 'fetch' and action of retrieving documentation content are purely…
Risk signalsAccepts URL/endpoint input (uri)
Documented attack patterns abuse exactly the kind of access fetch_android_doc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sceneview, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_android_doc:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_android_doc": {}
}
}fetch_android_doc is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetches the full text of a single stock Android documentation entry by its knowledge-base URI (kb://...), as returned by search_android_docs. Use this after search_android_docs to read a complete guide or API reference. Requires Google's android CLI on the MCP host's PATH (an optional runtime dependency); if the CLI is absent the tool returns clear install instructions instead of crashing. It is categorised as a Read tool in the Sceneview MCP Server, which means it retrieves data without modifying state.
fetch_android_doc accepts 1 parameter: uri. Required: uri. The full parameter table on this page comes from the server's own tool schema.
Register the Sceneview MCP server in PolicyLayer and add a rule for fetch_android_doc: 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 Sceneview. Nothing to install.
fetch_android_doc 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 fetch_android_doc 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 fetch_android_doc. 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.
fetch_android_doc is provided by the Sceneview MCP server (SceneView/sceneview). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sceneview, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 Sceneview tools catalogued and risk-classified — across an index of 43,000+ MCP servers.