cache_scan

Scan namespaced keys in the optional Redis companion cache

SERVERProject Guardian MCP SOURCE1999azzar/project-guardian-mcp-server

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/1999azzar-project-guardian-mcp-server/cache-scan.md

WHAT IT DOES

What cache_scan does on Project Guardian MCP

AI agents call cache_scan to retrieve information from Project Guardian 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 cache_scan is rated Low

The verb 'scan' combined with 'in the optional Redis companion cache' describes a retrieval/enumeration operation with no side effects. It lists or examines cache keys but does not create, modify, delete, or execute code. This is a straightforward Read category tool with low severity—misuse would only expose cached data rather than cause system damage.

From the tool's definition Tool name 'cache_scan' and description 'Scan namespaced keys in the optional Redis companion cache' indicate a read-only operation that queries cache keys without modifying or deleting data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cache_scan safely

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

cache_scan Allowed

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

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

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

FAQ

Questions about cache_scan

What does the cache_scan tool do? +

Scan namespaced keys in the optional Redis companion cache. It is categorised as a Read tool in the Project Guardian MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cache_scan? +

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

What risk level is cache_scan? +

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

Can I rate-limit cache_scan? +

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

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

cache_scan is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Project Guardian, and thousands of servers like it.

This server

All 38 Project Guardian tools →

Across the catalogue

cache_stats on ACE-MCP → The MCP Attack Database →

Guides

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