Get available mobile device models for Android/iOS fingerprinting
AI agents call get-mobile-devices to retrieve information from TgeBrowser MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely retrieves or lists available mobile device fingerprinting options. It has no side effects, does not execute code or browser automation, does not create or delete resources, and does not involve financial operations. It is a straightforward informational query with minimal security risk.
From the tool's definition Tool name 'get-mobile-devices' and description 'Get available mobile device models' indicate a query operation that retrieves a list of supported device models without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Get available mobile device models for Android/iOS fingerprinting. It is categorised as a Read tool in the TgeBrowser MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TgeBrowser MCP Server MCP server in PolicyLayer and add a rule for get-mobile-devices: 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 TgeBrowser MCP Server. Nothing to install.
get-mobile-devices 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 get-mobile-devices 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 get-mobile-devices. 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.
get-mobile-devices is provided by the TgeBrowser MCP Server MCP server (tuguang2025/tgebrowser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →