Critical Risk →

delete_from_fast_memory

Delete a query from Fast Memory.

How to control delete_from_fast_memory ↓

What delete_from_fast_memory does on ConnectWise API Gateway MCP Server

AI agents call delete_from_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 delete_from_fast_memory needs a policy

This tool irreversibly removes data (a saved query) from the Fast Memory cache. While the blast radius is limited to cached queries rather than production data, deletion is inherently irreversible and cannot be undone. This meets the Destructive category definition.

From the tool's definition Tool name contains 'delete' and description states 'Delete a query from Fast Memory.' The verb 'delete' is explicitly destructive.

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

How to control delete_from_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 delete_from_fast_memory:

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

delete_from_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 delete_from_fast_memory

What does the delete_from_fast_memory tool do? +

Delete a query 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 delete_from_fast_memory? +

Register the ConnectWise API Gateway MCP Server MCP server in PolicyLayer and add a rule for delete_from_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 delete_from_fast_memory? +

delete_from_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 delete_from_fast_memory? +

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

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

delete_from_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.