# workspace_status

Check which credential this MCP server is actually running on, what tier it grants, which workspace it is acting in, and whether that credential still works. Run this first when a tool returns 401 or 403 — it names the credential in play and what to do about it.

Agent View of the PolicyLayer registry record for `workspace_status`. HTML page: https://policylayer.com/tools/adrata-adrata-mcp/workspace-status

## Facts

- Tool: `workspace_status`
- Server: Adrata (`@adrata/adrata-mcp`) — https://policylayer.com/tools/adrata-adrata-mcp.md
- Install: `npx -y @adrata/adrata-mcp`
- Homepage: https://www.npmjs.com/package/@adrata/adrata-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why workspace_status is rated Low

Even though workspace_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call workspace_status to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Adrata:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "workspace_status": {}
  }
}
```

## Other tools on Adrata (277)

- `bulk_delete_buyer_groups` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/bulk-delete-buyer-groups.md
- `cancel_agent_task` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/cancel-agent-task.md
- `delete_action` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-action.md
- `delete_buyer_group` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-buyer-group.md
- `delete_company` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-company.md
- `delete_note` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-note.md
- `delete_opportunity` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-opportunity.md
- `delete_partner` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-partner.md
- `delete_person` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-person.md
- `delete_webhook` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-webhook.md
- `flag_work_item` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/flag-work-item.md
- `forget` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/forget.md
- `paper_delete_document` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/paper-delete-document.md
- `paper_revoke_share` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/paper-revoke-share.md
- `remove_buyer_group_member` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/remove-buyer-group-member.md
- `adrata_ai_tool_execute` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/adrata-ai-tool-execute.md
- `adrata_api_request` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/adrata-api-request.md
- `attribute_partner_to_deal` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/attribute-partner-to-deal.md
- `build_pursuit_command_center` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/build-pursuit-command-center.md
- `draft_workflow` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/draft-workflow.md
- `dry_run_workflow` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/dry-run-workflow.md
- `record_partner_consumption` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/record-partner-consumption.md
- `replay_workflow_run` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/replay-workflow-run.md
- `request_deployment` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/request-deployment.md
- `request_provider_action_execution` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/request-provider-action-execution.md
- `request_workflow_deployment` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/request-workflow-deployment.md
- `warmup_email` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/warmup-email.md
- `adrata_ai_tool_catalog` — Read — https://policylayer.com/tools/adrata-adrata-mcp/adrata-ai-tool-catalog.md
- `adrata_api_catalog` — Read — https://policylayer.com/tools/adrata-adrata-mcp/adrata-api-catalog.md
- `adrata_desktop_app_audit` — Read — https://policylayer.com/tools/adrata-adrata-mcp/adrata-desktop-app-audit.md
- …and 247 more: https://policylayer.com/tools/adrata-adrata-mcp.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=adrata-adrata-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adrata-adrata-mcp