get_access_key_info

THE RISK

Low Risk

Why get_access_key_info needs a policy

This tool retrieves metadata about access keys (signature type, expiry) without modifying state. It is a read operation. Severity is medium rather than low because access key details could aid an attacker in understanding authentication mechanisms, though the tool itself does not grant access or execute transactions.

From the tool's definition Tool name 'get_access_key_info' and description 'Get information about an access key' indicate a retrieval operation with no side effects. However, access key information could be sensitive.

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

POLICY

How to control get_access_key_info

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_access_key_info:

policy.json

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

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Tempo tools

Financial cancel_order Cancel an open order on the DEX. The remaining unfilled amount will be Financial cancel_scheduled_payment Cancel a pending scheduled payment before it executes. Financial swap_stablecoins Execute a stablecoin swap on Tempo DEX. Financial claim_rewards Claim all pending rewards for a TIP-20 token. Rewards are sent to your wallet Financial distribute_rewards Distribute rewards to all opted-in holders of a TIP-20 token. Financial mint_tokens Mint new TIP-20 tokens to a recipient address. Financial opt_in_rewards Opt into rewards for a TIP-20 token. After opting in, you will earn rewards Financial opt_out_rewards Opt out of rewards for a TIP-20 token. By default, any pending rewards will be

All 61 Tempo tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about get_access_key_info

What does the get_access_key_info tool do? +

Get information about an access key including signature type, expiry,. 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_access_key_info? +

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

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

Can I rate-limit get_access_key_info? +

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

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

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

CHECK YOUR STACK →