# get_my_profile

A read tool on the 1point3acres Toolkit MCP server.

Agent View of the PolicyLayer registry record for `get_my_profile`. HTML page: https://policylayer.com/tools/1point3acres-toolkit/get-my-profile

## Facts

- Tool: `get_my_profile`
- Server: 1point3acres Toolkit (`vivian-labs/1point3acres-toolkit`) — https://policylayer.com/tools/1point3acres-toolkit.md
- Homepage: https://github.com/vivian-labs/1point3acres-toolkit
- Risk category: Read (Low risk)
- Registry record: grade D, 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_my_profile",
    "arguments": {}
  }
}
```

## Why get_my_profile is rated Low

This tool retrieves profile information about the authenticated user with no side effects. It performs data retrieval only, matching the Read category definition. Severity is low because profile data exposure is limited in scope compared to other LinkedIn automation risks on this server (posting, connecting, messaging).

From the tool's own definition: "Tool name 'get_my_profile' indicates a retrieval operation. The function name follows read-pattern conventions (get_*). Server context shows tools like 'get_feed', 'get_inbox', 'get_company_profile' which are clearly read operations."

## Use case

AI agents call get_my_profile to retrieve information from 1point3acres Toolkit 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 1point3acres Toolkit:

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

## Other tools on 1point3acres Toolkit (32)

- `control_task` — Execute — https://policylayer.com/tools/1point3acres-toolkit/control-task.md
- `daily_run` — Execute — https://policylayer.com/tools/1point3acres-toolkit/daily-run.md
- `run_task` — Execute — https://policylayer.com/tools/1point3acres-toolkit/run-task.md
- `session_logout` — Execute — https://policylayer.com/tools/1point3acres-toolkit/session-logout.md
- `browse_board` — Read — https://policylayer.com/tools/1point3acres-toolkit/browse-board.md
- `collect_company` — Read — https://policylayer.com/tools/1point3acres-toolkit/collect-company.md
- `daily_history` — Read — https://policylayer.com/tools/1point3acres-toolkit/daily-history.md
- `daily_status` — Read — https://policylayer.com/tools/1point3acres-toolkit/daily-status.md
- `get_thread_detail` — Read — https://policylayer.com/tools/1point3acres-toolkit/get-thread-detail.md
- `get_unread_count` — Read — https://policylayer.com/tools/1point3acres-toolkit/get-unread-count.md
- `interviews_search` — Read — https://policylayer.com/tools/1point3acres-toolkit/interviews-search.md
- `list_notifications` — Read — https://policylayer.com/tools/1point3acres-toolkit/list-notifications.md
- `list_tasks` — Read — https://policylayer.com/tools/1point3acres-toolkit/list-tasks.md
- `organize_thread` — Read — https://policylayer.com/tools/1point3acres-toolkit/organize-thread.md
- `react_to_notification` — Read — https://policylayer.com/tools/1point3acres-toolkit/react-to-notification.md
- `recognize_media` — Read — https://policylayer.com/tools/1point3acres-toolkit/recognize-media.md
- `reply_thread` — Read — https://policylayer.com/tools/1point3acres-toolkit/reply-thread.md
- `reply_to_notification` — Read — https://policylayer.com/tools/1point3acres-toolkit/reply-to-notification.md
- `runtime_info` — Read — https://policylayer.com/tools/1point3acres-toolkit/runtime-info.md
- `search_threads` — Read — https://policylayer.com/tools/1point3acres-toolkit/search-threads.md
- `session_status` — Read — https://policylayer.com/tools/1point3acres-toolkit/session-status.md
- `stripe_collect` — Read — https://policylayer.com/tools/1point3acres-toolkit/stripe-collect.md
- `task_status` — Read — https://policylayer.com/tools/1point3acres-toolkit/task-status.md
- `user_profile` — Read — https://policylayer.com/tools/1point3acres-toolkit/user-profile.md
- `archive_media` — Write — https://policylayer.com/tools/1point3acres-toolkit/archive-media.md
- `create_collection_task` — Write — https://policylayer.com/tools/1point3acres-toolkit/create-collection-task.md
- `create_thread` — Write — https://policylayer.com/tools/1point3acres-toolkit/create-thread.md
- `interviews_export` — Write — https://policylayer.com/tools/1point3acres-toolkit/interviews-export.md
- `save_thread` — Write — https://policylayer.com/tools/1point3acres-toolkit/save-thread.md
- `session_login` — Write — https://policylayer.com/tools/1point3acres-toolkit/session-login.md
- …and 2 more: https://policylayer.com/tools/1point3acres-toolkit.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=1point3acres-toolkit · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1point3acres-toolkit