Low Risk

workspaces_info

Retrieve details about the workspaces in a specific workspace group

How to control workspaces_info ↓

AI agents call workspaces_info to retrieve information from SingleStore MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves metadata about workspaces without creating, modifying, deleting, or executing any operations. It is a pure read operation that queries existing workspace information, fitting the 'Read' category for data retrieval with no side effects.

From the tool's definition Tool name 'workspaces_info' and description 'Retrieve details about the workspaces in a specific workspace group' indicate a retrieval operation with no modification, deletion, or execution of external operations.

Documented attack patterns abuse exactly the kind of access workspaces_info 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 workspaces_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "workspaces_info": {}
  }
}

workspaces_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SingleStore 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the workspaces_info tool do? +

Retrieve details about the workspaces in a specific workspace group. It is categorised as a Read tool in the SingleStore MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on workspaces_info? +

Register the SingleStore MCP Server MCP server in PolicyLayer and add a rule for workspaces_info: 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 workspaces_info? +

workspaces_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit workspaces_info? +

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

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

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

Free to start. No card required.

24 SingleStore MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.