Low Risk

x402_publisher_verdict

Costs 1 credit ($0.02). The signed trust verdict on a single x402 publisher over TensorFeed's OWN on-chain settlement index: whether its Base payTo is actively settling, its 30-day settlement momentum, a shared-wallet risk flag, and the settlement evidence, with an AFTA-signed receipt. Versus the...

Part of the TensorFeed server.

x402_publisher_verdict 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 x402_publisher_verdict 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 x402_publisher_verdict 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": {
    "x402_publisher_verdict": {}
  }
}

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 x402_publisher_verdict 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 x402_publisher_verdict 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 x402_publisher_verdict tool do? +

Costs 1 credit ($0.02). The signed trust verdict on a single x402 publisher over TensorFeed's OWN on-chain settlement index: whether its Base payTo is actively settling, its 30-day settlement momentum, a shared-wallet risk flag, and the settlement evidence, with an AFTA-signed receipt. Versus the free x402_publisher_verdict_preview it adds the momentum band, the shared-wallet flag, and the settlement evidence (volume, count, last settled, daily series), with no rate limit. A not-indexed domain is no-charge. 10-minute freshness SLA. Get credits at tensorfeed.ai/developers/agent-payments. Strict premium, no free trial.. 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 x402_publisher_verdict? +

Register the TensorFeed MCP server in PolicyLayer and add a rule for x402_publisher_verdict: 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 x402_publisher_verdict? +

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

Can I rate-limit x402_publisher_verdict? +

Yes. Add a rate_limit block to the x402_publisher_verdict 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 x402_publisher_verdict completely? +

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

x402_publisher_verdict 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.