get_key

Get value by Redis key

SERVERNcp SOURCE@portel/ncp

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/io-github-portel-dev-ncp/get-key.md

WHAT IT DOES

What get_key does on Ncp

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

RISK

Why get_key is rated Low

This tool retrieves data from Redis by key lookup. It performs a read-only query operation without creating, modifying, deleting, or executing code. The blast radius of misuse is limited to unauthorized data disclosure, which is a low-severity information access concern.

From the tool's definition Tool description explicitly states 'Get value by Redis key' - a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_key safely

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

get_key Allowed

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

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

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

FAQ

Questions about get_key

What does the get_key tool do? +

Get value by Redis key. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_key? +

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

What risk level is get_key? +

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

Can I rate-limit get_key? +

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

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

get_key is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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