Low Risk

premium_x402_publisher_receipts

Per-publisher receipt feed for one x402-compliant domain across a from/to date range. Returns publisher meta (domain, pay_to_wallets, first_seen), window rollup (volume_usdc, count, avg_amount, daily_series), and attribution. VS FREE: get_x402_publishers tells you WHICH publishers exist but only ...

Part of the TensorFeed server.

premium_x402_publisher_receipts is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TENSORFEED →

Free to start. No card required.

AI agents call premium_x402_publisher_receipts to retrieve information from TensorFeed 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 premium_x402_publisher_receipts 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "premium_x402_publisher_receipts": {}
  }
}

See the full TensorFeed policy for all 79 tools.

Get this rule live on your own TensorFeed server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TENSORFEED →

View all 79 tools →

These attack patterns abuse exactly the kind of access premium_x402_publisher_receipts gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so premium_x402_publisher_receipts only ever does what you allow.

SECURE TENSORFEED →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the premium_x402_publisher_receipts tool do? +

Per-publisher receipt feed for one x402-compliant domain across a from/to date range. Returns publisher meta (domain, pay_to_wallets, first_seen), window rollup (volume_usdc, count, avg_amount, daily_series), and attribution. VS FREE: get_x402_publishers tells you WHICH publishers exist but only with rolled-up scalar counters. This endpoint composes the per-day rollup across a date range with avg_amount, daily series for charts, and structured attribution license metadata in one paid call. An agent building a per-publisher analytics dashboard would otherwise need to call get_x402_publishers + reconstruct daily series from get_x402_summary per-day (impossible because /summary returns ecosystem totals not per-publisher) or wait for the next free-tier expansion. The premium endpoint saves the integration overhead and serves a forensic / compliance-grade payload for $0.02. Forward-only index. Costs 1 credit ($0.02). Strict-premium; domain must exist in get_x402_publishers, otherwise 404.. It is categorised as a Read tool in the TensorFeed MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on premium_x402_publisher_receipts? +

Register the TensorFeed MCP server in PolicyLayer and add a rule for premium_x402_publisher_receipts: 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 TensorFeed. Nothing to install.

What risk level is premium_x402_publisher_receipts? +

premium_x402_publisher_receipts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit premium_x402_publisher_receipts? +

Yes. Add a rate_limit block to the premium_x402_publisher_receipts 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.

How do I block premium_x402_publisher_receipts completely? +

Set action: deny in the PolicyLayer policy for premium_x402_publisher_receipts. 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.

What MCP server provides premium_x402_publisher_receipts? +

premium_x402_publisher_receipts is provided by the TensorFeed MCP server (https://mcp.tensorfeed.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TensorFeed tool call.

Deterministic rules across all 79 TensorFeed 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.