# manage_workspace

Manage files and directories in the workspace sandbox. Supports nested paths (e.g.

Agent View of the PolicyLayer registry record for `manage_workspace`. HTML page: https://policylayer.com/tools/aaronsb-google-workspace-mcp/manage-workspace

## Facts

- Tool: `manage_workspace`
- Server: Google Workspace MCP Server (`aaronsb/google-workspace-mcp`) — https://policylayer.com/tools/aaronsb-google-workspace-mcp.md
- Homepage: https://github.com/aaronsb/google-workspace-mcp
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "manage_workspace",
    "arguments": {}
  }
}
```

## Why manage_workspace is rated Medium

The tool performs file and directory management operations which are write-class actions (create, update, organize). While the description is truncated and lacks detail on specific operations, 'manage' in this context typically implies creation and modification capabilities within a sandbox environment. Confidence is moderate (0.7) due to incomplete description and the sandbox constraint potentially limiting scope.

From the tool's own definition: "Tool description states 'Manage files and directories in the workspace sandbox' with support for nested paths, indicating file/directory creation, modification, and organization operations."

## Use case

AI agents use manage_workspace to create or update resources in Google Workspace MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace MCP Server environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Google Workspace MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_workspace": {
      "limits": [
        {
          "counter": "manage_workspace_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Google Workspace MCP Server (3)

- `queue_operations` — Execute — https://policylayer.com/tools/aaronsb-google-workspace-mcp/queue-operations.md
- `manage_accounts` — Write — https://policylayer.com/tools/aaronsb-google-workspace-mcp/manage-accounts.md
- `manage_scratchpad` — Write — https://policylayer.com/tools/aaronsb-google-workspace-mcp/manage-scratchpad.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=aaronsb-google-workspace-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aaronsb-google-workspace-mcp