# me

Get the signed-in user's profile (id, displayName, mail).

Agent View of the PolicyLayer registry record for `me`. HTML page: https://policylayer.com/tools/0xka13b-microsoft-mcps/me

## Facts

- Tool: `me`
- Server: Microsoft MCP (`0xka13b/microsoft-mcps`) — https://policylayer.com/tools/0xka13b-microsoft-mcps.md
- Homepage: https://github.com/0xka13b/microsoft-mcps
- 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": "me",
    "arguments": {}
  }
}
```

## Why me is rated Low

This tool retrieves user profile metadata without side effects. It queries the Microsoft Graph API for the authenticated user's information, which is a standard read operation. No data is created, modified, deleted, or executed. Severity is low because the exposed data is limited to the signed-in user's own public profile fields.

From the tool's own definition: "Tool description explicitly states 'Get the signed-in user's profile' with read-only fields (id, displayName, mail). The verb 'Get' and absence of modification language confirm retrieval-only behavior."

## Use case

AI agents call me to retrieve information from Microsoft MCP 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 Microsoft MCP:

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

## Other tools on Microsoft MCP (13)

- `delete_email` — Destructive — https://policylayer.com/tools/0xka13b-microsoft-mcps/delete-email.md
- `get_attachment` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/get-attachment.md
- `get_email` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/get-email.md
- `list_emails` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/list-emails.md
- `search_emails` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/search-emails.md
- `unified_search` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/unified-search.md
- `create_email_draft` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/create-email-draft.md
- `create_reply_draft` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/create-reply-draft.md
- `move_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/move-email.md
- `reply_all_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/reply-all-email.md
- `reply_to_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/reply-to-email.md
- `send_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/send-email.md
- `update_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/update-email.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=0xka13b-microsoft-mcps · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xka13b-microsoft-mcps