get_cache_status

THE RISK

Low Risk

Why get_cache_status needs a policy

This tool only retrieves cache configuration information without creating, modifying, deleting, or executing operations. It is a read-only query operation with no side effects. The low severity reflects minimal risk—exposing cache status details does not compromise data integrity or enable harmful actions.

From the tool's definition Tool name and description indicate 'get' operation and 'status' retrieval with no modification capabilities: 'Get current cache configuration status'

Documented attack patterns abuse exactly the kind of access get_cache_status gives an agent:

POLICY

How to control get_cache_status

PolicyLayer is an MCP gateway — it sits between your AI agents and PrestaShop MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_cache_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cache_status": {}
  }
}

get_cache_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register PrestaShop MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More PrestaShop MCP Server tools

Destructive clear_cache Clear PrestaShop cache Destructive delete_category Delete a category Destructive delete_product Delete a product Destructive remove_category_from_menu Remove a category from the main navigation menu tree Execute install_module Install a PrestaShop module Execute update_module_status Activate or deactivate a module Write add_category_to_menu Add a category to the main navigation menu tree Write add_main_menu_link Add a new main menu navigation link

All 34 PrestaShop MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_cache_status

What does the get_cache_status tool do? +

Get current cache configuration status. It is categorised as a Read tool in the PrestaShop MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cache_status? +

Register the PrestaShop MCP Server MCP server in PolicyLayer and add a rule for get_cache_status: 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 PrestaShop MCP Server. Nothing to install.

What risk level is get_cache_status? +

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

Can I rate-limit get_cache_status? +

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

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

get_cache_status is provided by the PrestaShop MCP Server MCP server (latinogino/prestashop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PrestaShop MCP Server tool call.

Start from PrestaShop MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →