brickognize_cache_clear

THE RISK

Critical Risk

Why brickognize_cache_clear needs a policy

Clearing a cache irreversibly removes stored data (cached API responses). While the data can be re-fetched from the upstream API, the local cached data is permanently deleted and cannot be undone without re-querying. This qualifies as Destructive.

From the tool's definition Clear the local cache of Rebrickable API responses

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

POLICY

How to control brickognize_cache_clear

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "brickognize_cache_clear"
  ]
}

brickognize_cache_clear disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Brickognize 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.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Brickognize MCP Server tools

Read brickognize_batch_identify Identify multiple LEGO items from local image files in a single call. Read brickognize_batch_part_details Get details for multiple LEGO parts in a single call: colors, and which sets contain each Read brickognize_health Check whether the Brickognize image recognition API is online and responsive. Read brickognize_minifig_details Get detailed information about a LEGO minifigure by its ID: name, parts count, Read brickognize_part_details Get detailed information about a LEGO part by its ID: available colors, Read brickognize_set_details Get detailed information about a LEGO set by its number: year, theme, piece count,

All 7 Brickognize MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Brickognize MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about brickognize_cache_clear

What does the brickognize_cache_clear tool do? +

Clear the local cache of Rebrickable API responses (part details, set inventories, etc.). It is categorised as a Destructive tool in the Brickognize MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on brickognize_cache_clear? +

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

What risk level is brickognize_cache_clear? +

brickognize_cache_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit brickognize_cache_clear? +

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

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

brickognize_cache_clear is provided by the Brickognize MCP Server MCP server (nazarlysyi/brickscope). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Brickognize MCP Server tool call.

Start from Brickognize 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 →