// MCP TOOL REFERENCE

TRACKING TOOLS

8 tools from the Tracking MCP Server, categorised by risk level.

READ TOOLS

get_developer_name Get the current logged-in developer's display name (nickName), used for querying tracking list get_tracking_screenshot Get the screenshot/attachment image for a tracking record. Returns the image directly so AI can analyze it. list_product_types List platform types (e.g. iOS, Android, Web) for a specific product list_product_versions List available versions for a product list_products List all available product names in the tracking platform search_tracking Search tracking/burial point records by developer name and product. Returns paginated list with details including PageID, ActionID, attributes, and... tracking-auth Login to Intsig Data Studio (tracking platform) via SSO. Opens browser for authentication.

DESTRUCTIVE TOOLS

tracking-logout Clear saved tracking platform credentials and logout.

// FAQ

How many tools does the Tracking MCP server have? +

The Tracking MCP server exposes 8 tools across 2 categories: Read, Destructive.

How do I enforce policies on Tracking tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Tracking server.

What risk categories do Tracking tools fall into? +

Tracking tools are categorised as Read (7), Destructive (1). Each category has a recommended default policy.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →