Search tracking/burial point records by developer name and product. Returns paginated list with details including PageID, ActionID, attributes, and status.
Part of the Tracking MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call search_tracking to retrieve information from Tracking without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_tracking only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
search_tracking:
rules:
- action: allowSee the full Tracking policy for all 8 tools.
Agents calling read-class tools like search_tracking have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Search tracking/burial point records by developer name and product. Returns paginated list with details including PageID, ActionID, attributes, and status.. It is categorised as a Read tool in the Tracking MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for search_tracking. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Tracking MCP server.
search_tracking 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 search_tracking rule in your Intercept 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 Intercept policy for search_tracking. 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.
search_tracking is provided by the Tracking MCP server (@camscanner/tracking-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.