Critical Risk →

clear_fast_memory

Clear all queries from Fast Memory.

How to control clear_fast_memory ↓

What clear_fast_memory does on ConnectWise API Gateway MCP Server

AI agents call clear_fast_memory to permanently remove resources in ConnectWise API Gateway MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why clear_fast_memory needs a policy

This tool permanently removes all cached/stored query data from the Fast Memory system. While not directly financial or operating on production user data (based on context as a caching layer), it irreversibly destroys a data store.

From the tool's definition 'Clear all queries from Fast Memory' - the verb 'clear' combined with 'all' indicates irreversible deletion of stored data without conditional filtering or undo capability.

Risk signalsBulk/mass operation — affects multiple targets

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

How to control clear_fast_memory

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_fast_memory"
  ]
}

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

  1. Create a free account and register ConnectWise API Gateway MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about clear_fast_memory

What does the clear_fast_memory tool do? +

Clear all queries from Fast Memory. It is categorised as a Destructive tool in the ConnectWise API Gateway 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 clear_fast_memory? +

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

What risk level is clear_fast_memory? +

clear_fast_memory 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 clear_fast_memory? +

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

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

clear_fast_memory is provided by the ConnectWise API Gateway MCP Server MCP server (jasondsmith72/cwm-api-gateway-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ConnectWise API Gateway MCP Server tool call.

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

Free to start. No card required.

11 ConnectWise API Gateway MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.