create_access_key

Create a new P256 access key (session key) for delegated signing.

SERVERTempo SOURCEarome3/tempo-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/create-access-key.md

WHAT IT DOES

What create_access_key does on Tempo

AI agents use create_access_key to create or update resources in Tempo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tempo environment.

RISK

Why create_access_key is rated Medium

This tool creates a new cryptographic access key that enables delegated signing authority. While it is a Write operation (creating a resource), it carries high severity because a misused or maliciously created session key could allow an attacker to delegate signing rights on the blockchain, potentially enabling unauthorized transactions or payments on the Tempo stablecoin platform.

From the tool's definition Create a new P256 access key (session key) for delegated signing

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_access_key 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 create_access_key, this is the rule to start with:

create_access_key Rate-limited

create_access_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_access_key": {
      "limits": [
        {
          "counter": "create_access_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about create_access_key

What does the create_access_key tool do? +

Create a new P256 access key (session key) for delegated signing. It is categorised as a Write tool in the Tempo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_access_key? +

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

create_access_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_access_key? +

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

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

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

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →