list_active_nonce_keys

List all nonce keys that have been used (have nonce > 0) for an address.

SERVERTempo SOURCEarome3/tempo-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/list-active-nonce-keys.md

WHAT IT DOES

What list_active_nonce_keys does on Tempo

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

RISK

Why list_active_nonce_keys is rated Low

This tool retrieves historical nonce key information for an address without creating, modifying, deleting, or executing any state-changing operations. It is a simple informational query that provides transparency into past transactions but cannot alter blockchain state or trigger payments.

From the tool's definition Tool description states 'List all nonce keys' which is a retrieval operation with no modifications. The verb 'list' and the data being retrieved (nonce keys that have been used) are read-only queries.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_active_nonce_keys safely

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

list_active_nonce_keys Allowed

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

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

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

FAQ

Questions about list_active_nonce_keys

What does the list_active_nonce_keys tool do? +

List all nonce keys that have been used (have nonce > 0) for an address. It is categorised as a Read tool in the Tempo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_active_nonce_keys? +

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

What risk level is list_active_nonce_keys? +

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

Can I rate-limit list_active_nonce_keys? +

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

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

list_active_nonce_keys is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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