Low Risk

get_nonce_for_key

Get the current transaction nonce for a specific nonce key (0-255).

How to control get_nonce_for_key ↓

What get_nonce_for_key does on Tempo

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

Low Risk

Why get_nonce_for_key needs a policy

This tool queries and returns the current nonce value for transaction sequencing purposes. It performs a read-only operation that neither modifies state, executes external operations, nor affects financial holdings. The nonce is informational metadata needed to construct valid transactions, but retrieving it causes no state change or irreversible action.

From the tool's definition Tool name is 'get_nonce_for_key' and description states 'Get the current transaction nonce' — a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_nonce_for_key gives an agent:

How to control get_nonce_for_key

PolicyLayer is an MCP gateway — it sits between your AI agents and Tempo, and nothing reaches the server without passing your rules. This is the rule we recommend for get_nonce_for_key:

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

get_nonce_for_key is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tempo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_nonce_for_key

What does the get_nonce_for_key tool do? +

Get the current transaction nonce for a specific nonce key (0-255). 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 get_nonce_for_key? +

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

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

Can I rate-limit get_nonce_for_key? +

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

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

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

Enforce policy on every Tempo tool call.

Start from Tempo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

61 Tempo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.