# get_context

Get the user

Agent View of the PolicyLayer registry record for `get_context`. HTML page: https://policylayer.com/tools/4da-mcp-server/get-context

## Facts

- Tool: `get_context`
- Server: 4da (`4DA-Systems/4da-mcp-server`) — https://policylayer.com/tools/4da-mcp-server.md
- Homepage: https://github.com/4DA-Systems/4da-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade B, 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_context",
    "arguments": {}
  }
}
```

## Why get_context is rated Low

This tool retrieves user context/information with no side effects or data modification. It fits the Read category as a simple query operation. Severity is low since it only accesses user context data without ability to modify, delete, or execute operations. Confidence is 0.85 rather than higher because the description is extremely sparse and doesn't fully clarify the scope of what user information is exposed.

From the tool's own definition: "Tool name 'get_context' with description 'Get the user' indicates retrieval of user information without modification. The verb 'Get' and context of reading user data aligns with data retrieval operations."

## Use case

AI agents call get_context to retrieve information from 4da 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 4da:

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

## Other tools on 4da (14)

- `check_decision_alignment` — Read — https://policylayer.com/tools/4da-mcp-server/check-decision-alignment.md
- `dependency_health` — Read — https://policylayer.com/tools/4da-mcp-server/dependency-health.md
- `developer_dna` — Read — https://policylayer.com/tools/4da-mcp-server/developer-dna.md
- `ecosystem_pulse` — Read — https://policylayer.com/tools/4da-mcp-server/ecosystem-pulse.md
- `get_actionable_signals` — Read — https://policylayer.com/tools/4da-mcp-server/get-actionable-signals.md
- `get_relevant_content` — Read — https://policylayer.com/tools/4da-mcp-server/get-relevant-content.md
- `knowledge_gaps` — Read — https://policylayer.com/tools/4da-mcp-server/knowledge-gaps.md
- `record_feedback` — Read — https://policylayer.com/tools/4da-mcp-server/record-feedback.md
- `upgrade_impact` — Read — https://policylayer.com/tools/4da-mcp-server/upgrade-impact.md
- `vulnerability_scan` — Read — https://policylayer.com/tools/4da-mcp-server/vulnerability-scan.md
- `what_should_i_know` — Read — https://policylayer.com/tools/4da-mcp-server/what-should-i-know.md
- `agent_memory` — Write — https://policylayer.com/tools/4da-mcp-server/agent-memory.md
- `decision_memory` — Write — https://policylayer.com/tools/4da-mcp-server/decision-memory.md
- `upgrade_planner` — Write — https://policylayer.com/tools/4da-mcp-server/upgrade-planner.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=4da-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/4da-mcp-server
