data_freshness

Return token freshness and the latest synchronization run.

SERVERzoraHoldersAI SOURCEmarblerace/zoraHoldersAI

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/zoraholdersai/data-freshness.md

WHAT IT DOES

What data_freshness does on zoraHoldersAI

AI agents call data_freshness to retrieve information from zoraHoldersAI without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why data_freshness is rated Low

Even though data_freshness only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs data_freshness safely

PolicyLayer is an MCP gateway: it sits between your AI agents and zoraHoldersAI, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For data_freshness, this is the rule to start with:

data_freshness Allowed

data_freshness is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "data_freshness": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect zoraHoldersAI, apply this rule, and every data_freshness call is checked against it from then on.

FAQ

Questions about data_freshness

What does the data_freshness tool do? +

Return token freshness and the latest synchronization run. It is categorised as a Read tool in the zoraHoldersAI MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on data_freshness? +

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

What risk level is data_freshness? +

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

Can I rate-limit data_freshness? +

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

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

data_freshness is provided by the zoraHoldersAI MCP server (marblerace/zoraHoldersAI). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on zoraHoldersAI, and thousands of servers like it.

This server

All 4 zoraHoldersAI tools →

Across the catalogue

collect_devtools_data on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →