Medium Risk

select_workspace

Select a workspace to use

Risk signalsChanges active workspace context

Part of the Render server.

select_workspace can modify Render data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE RENDER →

Free to start. No card required.

AI agents use select_workspace to create or modify resources in Render. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call select_workspace repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Render.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "select_workspace": {
      "limits": [
        {
          "counter": "select_workspace_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Render policy for all 21 tools.

Get this rule live on your own Render server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY RENDER →

View all 21 tools →

These attack patterns abuse exactly the kind of access select_workspace gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so select_workspace only ever does what you allow.

SECURE RENDER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the select_workspace tool do? +

Select a workspace to use. It is categorised as a Write tool in the Render MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on select_workspace? +

Register the Render MCP server in PolicyLayer and add a rule for select_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 Render. Nothing to install.

What risk level is select_workspace? +

select_workspace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit select_workspace? +

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

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

select_workspace is provided by the Render MCP server (@render-oss/render-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Render tool call.

Deterministic rules across all 21 Render tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.