AI agents use create_starter_workspace to create or update resources in SingleStore MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SingleStore MCP Server environment.
This tool creates a new starter workspace in SingleStore, which is a Write operation. It provisions a new environment/resource but is reversible (workspaces can be deleted). Misuse could lead to unwanted resource creation and potential costs, but it does not directly move money or irreversibly destroy data.
From the tool's definition 'Create a new starter workspace' — creates a new resource
Documented attack patterns abuse exactly the kind of access create_starter_workspace gives an agent:
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 create_starter_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"create_starter_workspace": {
"limits": [
{
"counter": "create_starter_workspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_starter_workspace stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new starter workspace. It is categorised as a Write tool in the SingleStore MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SingleStore MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_starter_workspace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
Deterministic rules across all 24 SingleStore MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 SingleStore MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.