Low Risk

get-current-account

Get the current Cloud Redis account

How to control get-current-account ↓

AI agents call get-current-account to retrieve information from Redis Cloud API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries account information without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves data about the current account. The low severity reflects that account metadata retrieval has minimal blast radius even if misused by an AI agent.

From the tool's definition Tool name 'get-current-account' and description 'Get the current Cloud Redis account' indicate a retrieval operation with no modification or execution of side effects.

Documented attack patterns abuse exactly the kind of access get-current-account gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Redis Cloud API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-current-account:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-current-account": {}
  }
}

get-current-account 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 Redis Cloud API MCP Server — 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.

Go deeper

What does the get-current-account tool do? +

Get the current Cloud Redis account. It is categorised as a Read tool in the Redis Cloud API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-current-account? +

Register the Redis Cloud API MCP Server MCP server in PolicyLayer and add a rule for get-current-account: 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 Redis Cloud API MCP Server. Nothing to install.

What risk level is get-current-account? +

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

Can I rate-limit get-current-account? +

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

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

get-current-account is provided by the Redis Cloud API MCP Server MCP server (redis/mcp-redis-cloud). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Redis Cloud API MCP Server tool call.

Deterministic rules across all 18 Redis Cloud API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 Redis Cloud API MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.