ToolTrust
A2/100
Smithery

ren89752-aidroid

mcpsmithery

@Smithery

Search official Microsoft and Azure documentation to ground your answers with trusted, first-party content. Fetch complete articles when you need step-by-step guides, troubleshooting, and prerequisites. Retrieve the latest official code samples across languages to accelerate implementation.

By Smithery | 9 findings | Scanned 7/3/2026 | tooltrust-scanner/v0.3.19

3 Low6 Info

Risk Summary

Safe With Normal Controls

Excessive Permissions is the main signal, but overall risk remains within an acceptable range.

Potential impact: The agent may gain overly broad access to files, network, databases, or execution capabilities.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (9)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×3

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    microsoft_docs_searchmicrosoft_code_sample_searchmicrosoft_docs_fetch

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-002

    ⚠️Excessive Permissions ×3

    declared capabilities: network access, database access

    microsoft_docs_search

    declared capabilities: code/command execution, network access, database access

    microsoft_code_sample_search

    declared capabilities: network access

    microsoft_docs_fetch

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×3

    Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    microsoft_docs_searchmicrosoft_code_sample_searchmicrosoft_docs_fetch

    Fix: Review and remediate the identified issue.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y ren89752-aidroid"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)