store.kv-scan

STORE: list keys in a namespace, scoped to YOUR wallet...

SERVERMcp SOURCE@2sio/mcp

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-2s-io-mcp/store.kv-scan.md

WHAT IT DOES

What store.kv-scan does on Mcp

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

RISK

Why store.kv-scan is rated Low

This tool retrieves or queries data (keys in a namespace) without modifying, deleting, or executing anything. It has minimal blast radius—even if misused by an agent, it only exposes keys the wallet owner already has access to. This is a straightforward Read category operation.

From the tool's definition Tool name includes 'scan' and description states 'list keys in a namespace'. The verb 'list' is a read-only retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs store.kv-scan safely

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

store.kv-scan Allowed

store.kv-scan 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": {
    "store.kv-scan": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every store.kv-scan call is checked against it from then on.

FAQ

Questions about store.kv-scan

What does the store.kv-scan tool do? +

STORE: list keys in a namespace, scoped to YOUR wallet. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on store.kv-scan? +

Register the MCP server in PolicyLayer and add a rule for store.kv-scan: 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 Mcp. Nothing to install.

What risk level is store.kv-scan? +

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

Can I rate-limit store.kv-scan? +

Yes. Add a rate_limit block to the store.kv-scan 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 store.kv-scan completely? +

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

store.kv-scan is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

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