Choose from available organizations (only available when API key environment variable is not set)
AI agents use choose_organization 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 changes application state (active organization context) in a reversible manner. While it doesn't create/modify persistent data directly, it alters the execution context for subsequent operations, similar to a 'select database' or 'use schema' command. It's not Read (no data retrieval), not Execute (no code/commands), not Destructive (reversible), and not Financial.
From the tool's definition Tool description states it allows choosing from available organizations, implying it sets or switches organizational context. This is a stateful operation that modifies the user's session or configuration state, even if not persisting to a database.
Documented attack patterns abuse exactly the kind of access choose_organization 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 choose_organization:
{
"version": "1",
"default": "deny",
"tools": {
"choose_organization": {
"limits": [
{
"counter": "choose_organization_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}choose_organization 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.
Choose from available organizations (only available when API key environment variable is not set). 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 choose_organization: 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.
choose_organization 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 choose_organization 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 choose_organization. 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.
choose_organization 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.