orgo_workspace_by_name

ServerOrgo MCP Server
CategoryRead

WHAT IT DOES

What orgo_workspace_by_name does on Orgo MCP Server

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

THE RISK

Low Risk

Why orgo_workspace_by_name needs a policy

This tool performs a simple lookup/query operation, retrieving workspace details by name. It has no side effects, does not modify data, and does not execute any commands. It is purely a read/fetch operation.

From the tool's definition Look up a workspace by name instead of ID. Returns workspace details if found.

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

POLICY

How to control orgo_workspace_by_name

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "orgo_workspace_by_name": {}
  }
}

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

Create a free account and register Orgo 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.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Orgo MCP Server tools

Destructive orgo_delete_computer Permanently delete a computer and all its data. Cannot be undone. Use only when explicitly Destructive orgo_delete_workspace Permanently delete a workspace and all of its computers. Cannot be undone. Use only when e Destructive orgo_restart_computer Restart a computer. Useful for recovering from unresponsive states. Use when commands hang Execute orgo_bash Execute a bash command on the VM. Uses WebSocket terminal (preferred) with REST API fallba Execute orgo_ensure_running Ensure a computer is running. Resumes suspended VMs automatically. Idempotent. Use before Execute orgo_exec Execute Python code on the computer. Returns output or error details. Use for computation, Execute orgo_wait Pause execution on the VM for a fixed duration. Useful for sequencing actions between scre Execute orgo_click Click at pixel (x, y) coordinates on the VM display. Coordinates are in 1280x720 model spa

All 28 Orgo MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about orgo_workspace_by_name

What does the orgo_workspace_by_name tool do? +

Look up a workspace by name instead of ID. Returns workspace details if found. Use when the workspace name comes from configuration (env var, user input) but no ID is on hand — saves a list_workspaces + filter step. It is categorised as a Read tool in the Orgo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on orgo_workspace_by_name? +

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

What risk level is orgo_workspace_by_name? +

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

Can I rate-limit orgo_workspace_by_name? +

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

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

orgo_workspace_by_name is provided by the Orgo MCP Server MCP server (nickvasilescu/orgo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Orgo MCP Server tool call.

Start from Orgo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

28 Orgo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.