This record as markdown: /tools/io-github-portel-dev-ncp/cache-get.md
What cache_get does on Ncp
AI agents call cache_get 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.
Why cache_get is rated Low
This tool performs a simple data retrieval operation from a cache store with no side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal - an attacker could only read cached data that may already be accessible through other means, posing no risk to data integrity, system execution, or financial operations.
From the tool's definition 'Retrieve data from Memcached' - the verb 'Retrieve' and the function name 'cache_get' both indicate a read-only operation that queries cached data without modification.
Attacks that exploit this kind of access
The rule that runs cache_get 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 cache_get, this is the rule to start with:
cache_get is read-only, so it stays allowed. 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 cache_get call is checked against it from then on.
Questions about cache_get
Retrieve data from Memcached. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.
Register the Ncp MCP server in PolicyLayer and add a rule for cache_get: 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.
cache_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cache_get 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 cache_get. 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.
cache_get 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