This record as markdown: /tools/io-github-portel-dev-ncp/set-key.md
What set_key does on Ncp
AI agents use set_key to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why set_key is rated Medium
This tool modifies data in Redis by setting key-value pairs. While the operation is reversible (keys can be updated or deleted later), it has side effects on persistent data storage. This places it in the Write category rather than Read (which would be retrieval only) or Destructive (which would be irreversible).
From the tool's definition 'Set Redis key-value pair' indicates creating or modifying key-value pairs in a Redis database. Redis SET operations are reversible writes that can be updated or overwritten.
Attacks that exploit this kind of access
The rule that runs set_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 set_key, this is the rule to start with:
set_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every set_key call is checked against it from then on.
Questions about set_key
Set Redis key-value pair. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for set_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.
set_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_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.
Set action: deny in the PolicyLayer policy for set_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.
set_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.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue