<tool_description> Track delivery of an enriched snippet and bill the advertiser. Creates a ledger entry and decrements the media buy budget. </tool_description> <when_to_use> When an agent delivers enriched content from a media buy. Each delivery is billed by snippet tier: - basic: 10¢, standard...
Part of the Discovery server.
Free to start. No card required.
AI agents call track_enriched_snippet to retrieve information from Discovery 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 track_enriched_snippet 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.
{
"version": "1",
"default": "deny",
"tools": {
"track_enriched_snippet": {}
}
}See the full Discovery policy for all 19 tools.
These attack patterns abuse exactly the kind of access track_enriched_snippet gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
<tool_description> Track delivery of an enriched snippet and bill the advertiser. Creates a ledger entry and decrements the media buy budget. </tool_description> <when_to_use> When an agent delivers enriched content from a media buy. Each delivery is billed by snippet tier: - basic: 10¢, standard: 50¢, rich: 150¢, premium: 300¢ (CHF centimes). </when_to_use> <combination_hints> activate (enriched_snippet buy) → track_enriched_snippet per delivery. get_campaign_report shows cumulative tracking. </combination_hints> <output_format> Event ID, charged amount, platform fee, net payout, remaining budget. </output_format>. It is categorised as a Read tool in the Discovery MCP Server, which means it retrieves data without modifying state.
Register the Discovery MCP server in PolicyLayer and add a rule for track_enriched_snippet: 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 Discovery. Nothing to install.
track_enriched_snippet 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 track_enriched_snippet 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 track_enriched_snippet. 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.
track_enriched_snippet is provided by the Discovery MCP server (https://mcp.nexbid.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Discovery tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.