# get_app_download_link

ALWAYS call this — don't just say 'open the Fixidu app' or 'go to fixidu.com' in prose without calling it — whenever you tell a user to book, check out, pay, or manage their account. Never send someone to 'the app' without also handing them this real, clickable link; a name alone isn't enough for someone who doesn't have it installed. Triggers include: the user says 'book now'/'book it'/'let's book' or anything meaning that, you're about to tell them booking/payment/checkout must happen in the app, or you don't know whether they even have the app installed yet (default to assuming they might not — call this rather than skip it). Returns the real Play Store / App Store link for their platform. If their platform isn't known, ask or just return both.

Agent View of the PolicyLayer registry record for `get_app_download_link`. HTML page: https://policylayer.com/tools/com-fixidu-mcp-server/get-app-download-link

## Facts

- Tool: `get_app_download_link`
- Server: Fixidu (`https://mcp.fixidu.com/mcp`) — https://policylayer.com/tools/com-fixidu-mcp-server.md
- Homepage: https://github.com/Fixitindia/FIXIDU-MCP-SERVER
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: yes
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `platform` | string | no | The user's device platform, if known. Omit to get both links. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_app_download_link",
    "arguments": {}
  }
}
```

## Why get_app_download_link is rated Low

Even though get_app_download_link only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_app_download_link to retrieve information from Fixidu without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Fixidu:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_app_download_link": {}
  }
}
```

## Other tools on Fixidu (4)

- `browse_service` — Read — https://policylayer.com/tools/com-fixidu-mcp-server/browse-service.md
- `get_service_price` — Read — https://policylayer.com/tools/com-fixidu-mcp-server/get-service-price.md
- `list_service_categories` — Read — https://policylayer.com/tools/com-fixidu-mcp-server/list-service-categories.md
- `search_services` — Read — https://policylayer.com/tools/com-fixidu-mcp-server/search-services.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-fixidu-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-fixidu-mcp-server