terminate_starter_workspace

THE RISK

Critical Risk

Terminating a workspace is a destructive, irreversible action that removes the running environment and potentially all associated data and configurations. This cannot be undone, making it Destructive with high severity given the blast radius of losing an entire workspace.

From the tool's definition "Terminate an existing starter workspace" — termination is irreversible destruction of the workspace and its associated resources

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

HOW TO CONTROL TERMINATE_STARTER_WORKSPACE

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

policy.json

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

terminate_starter_workspace 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 SingleStore 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

More SingleStore MCP Server tools

Destructive delete_job Delete an existing job Destructive stage_delete Delete a file or folder from Stage Execute run_sql Execute SQL operations on a connected workspace Execute create_job_from_notebook Create a scheduled job from a notebook Execute resume_workspace Resume a suspended workspace Write choose_organization Choose from available organizations (only available when API key environment variable is n Write create_notebook_file Create a new notebook file in SingleStore Spaces Write create_starter_workspace Create a new starter workspace

All 24 SingleStore MCP Server tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in SingleStore 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.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the terminate_starter_workspace tool do? +

Terminate an existing starter workspace. It is categorised as a Destructive tool in the SingleStore 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 terminate_starter_workspace? +

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

What risk level is terminate_starter_workspace? +

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

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

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

terminate_starter_workspace is provided by the SingleStore MCP Server MCP server (singlestore-labs/mcp-server-singlestore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SingleStore MCP Server tool call.

Deterministic rules across all 24 SingleStore MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN SINGLESTORE →

Free to start. No card required.

24 SingleStore MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT TERMINATE_STARTER_WORKSPACE ON SINGLESTORE MCP SERVER DOES

// THE RISK

// HOW TO CONTROL TERMINATE_STARTER_WORKSPACE

// EXPLORE