# developer_dna

Export your Developer DNA — a comprehensive profile of your tech identity built from project scans, explicit interests, and local interaction history. Includes primary stack, adjacent tech, top dependencies, engaged topics, blind spots, source engagement rates, and aggregate stats.

Agent View of the PolicyLayer registry record for `developer_dna`. HTML page: https://policylayer.com/tools/4da-mcp-server/developer-dna

## Facts

- Tool: `developer_dna`
- 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": "developer_dna",
    "arguments": {}
  }
}
```

## Why developer_dna is rated Low

Even though developer_dna 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 developer_dna 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": {
    "developer_dna": {}
  }
}
```

## 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
- `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_context` — Read — https://policylayer.com/tools/4da-mcp-server/get-context.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
