vision.render.cache_info

Show the cache identity for render requests.

SERVERVisionmcp SOURCEjoshuahickscorp/visionmcp

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/visionmcp/vision.render.cache-info.md

WHAT IT DOES

What vision.render.cache_info does on Visionmcp

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

RISK

Why vision.render.cache_info is rated Low

This tool queries and displays cache information about render requests. It performs a read-only operation with no side effects, data modification, or external state changes. The low severity reflects minimal impact if misused—an agent could only view cache metadata, not alter systems or data.

From the tool's definition Tool name includes 'cache_info' and description states 'Show the cache identity', indicating retrieval of cache metadata without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vision.render.cache_info safely

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

vision.render.cache_info Allowed

vision.render.cache_info 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": {
    "vision.render.cache_info": {}
  }
}

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

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

FAQ

Questions about vision.render.cache_info

What does the vision.render.cache_info tool do? +

Show the cache identity for render requests. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vision.render.cache_info? +

Register the Vision MCP server in PolicyLayer and add a rule for vision.render.cache_info: 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 Visionmcp. Nothing to install.

What risk level is vision.render.cache_info? +

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

Can I rate-limit vision.render.cache_info? +

Yes. Add a rate_limit block to the vision.render.cache_info 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 vision.render.cache_info completely? +

Set action: deny in the PolicyLayer policy for vision.render.cache_info. 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 vision.render.cache_info? +

vision.render.cache_info is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vision, and thousands of servers like it.

This server

All 376 Vision tools →

Across the catalogue

The MCP Attack Database →

Guides

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