# get-user-by-id

Gets a user by their unique identifier

Agent View of the PolicyLayer registry record for `get-user-by-id`. HTML page: https://policylayer.com/tools/mcp-dev/get-user-by-id

## Facts

- Tool: `get-user-by-id`
- Server: Mcp Dev (`@umbraco-cms/mcp-dev`) — https://policylayer.com/tools/mcp-dev.md
- Install: `npx -y @umbraco-cms/mcp-dev`
- Homepage: git+https://github.com/umbraco/Umbraco-CMS-MCP-Dev.git
- 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": "get-user-by-id",
    "arguments": {}
  }
}
```

## Why get-user-by-id is rated Low

This tool retrieves user information by ID. It is a query operation that reads data without modifying, deleting, or executing code. The severity is low because accessing user data via ID lookup poses minimal risk if an AI agent uses it—it returns information that is likely accessible through normal administrative channels in the CMS.

From the tool's own definition: "Tool name 'get-user-by-id' and description 'Gets a user by their unique identifier' indicate a retrieval operation with no data modification or side effects."

## Use case

AI agents call get-user-by-id to retrieve information from Mcp Dev 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 Mcp Dev:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-user-by-id": {}
  }
}
```

## Other tools on Mcp Dev (418)

- `create-document-version-rollback` — Destructive — https://policylayer.com/tools/mcp-dev/create-document-version-rollback.md
- `delete-data-type` — Destructive — https://policylayer.com/tools/mcp-dev/delete-data-type.md
- `delete-data-type-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-data-type-folder.md
- `delete-dictionary-item` — Destructive — https://policylayer.com/tools/mcp-dev/delete-dictionary-item.md
- `delete-document` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document.md
- `delete-document-blueprint` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-blueprint.md
- `delete-document-blueprint-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-blueprint-folder.md
- `delete-document-public-access` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-public-access.md
- `delete-document-recycle-bin-item` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-recycle-bin-item.md
- `delete-document-type` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-type.md
- `delete-document-type-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-document-type-folder.md
- `delete-element` — Destructive — https://policylayer.com/tools/mcp-dev/delete-element.md
- `delete-element-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-element-folder.md
- `delete-element-folder-from-recycle-bin` — Destructive — https://policylayer.com/tools/mcp-dev/delete-element-folder-from-recycle-bin.md
- `delete-element-from-recycle-bin` — Destructive — https://policylayer.com/tools/mcp-dev/delete-element-from-recycle-bin.md
- `delete-from-recycle-bin` — Destructive — https://policylayer.com/tools/mcp-dev/delete-from-recycle-bin.md
- `delete-language` — Destructive — https://policylayer.com/tools/mcp-dev/delete-language.md
- `delete-log-viewer-saved-search-by-name` — Destructive — https://policylayer.com/tools/mcp-dev/delete-log-viewer-saved-search-by-name.md
- `delete-media` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media.md
- `delete-media-from-recycle-bin` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media-from-recycle-bin.md
- `delete-media-recycle-bin-item` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media-recycle-bin-item.md
- `delete-media-type` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media-type.md
- `delete-media-type-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-media-type-folder.md
- `delete-member` — Destructive — https://policylayer.com/tools/mcp-dev/delete-member.md
- `delete-member-group` — Destructive — https://policylayer.com/tools/mcp-dev/delete-member-group.md
- `delete-member-type` — Destructive — https://policylayer.com/tools/mcp-dev/delete-member-type.md
- `delete-partial-view` — Destructive — https://policylayer.com/tools/mcp-dev/delete-partial-view.md
- `delete-partial-view-folder` — Destructive — https://policylayer.com/tools/mcp-dev/delete-partial-view-folder.md
- `delete-redirect` — Destructive — https://policylayer.com/tools/mcp-dev/delete-redirect.md
- `delete-script` — Destructive — https://policylayer.com/tools/mcp-dev/delete-script.md
- …and 388 more: https://policylayer.com/tools/mcp-dev.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=mcp-dev · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/mcp-dev
