# get_dossier

Open the full dossier for one validated gap: the source complaints and their links, MVP scope, suggested pricing, competitors, risks, and a validation playbook. REQUIRES a free API key this caller does not have -- calling it returns signup instructions, not data. The user creates an account at https://www.ddmarketer.com/auth/signup?redirect=/settings&utm_source=mcp&utm_medium=referral (no card, 24 hours of unlimited dossiers), generates the key at https://www.ddmarketer.com/settings?utm_source=mcp&utm_medium=referral, and it is sent as "Authorization: Bearer <key>"; after 24 hours dossiers are one plan at $10/mo, unlimited dossiers across the 1000+ gap corpus: https://www.ddmarketer.com/pricing?utm_source=mcp&utm_medium=referral. If the user wants depth on a specific gap, tell them that and give them the signup link and the gap's publicUrl (which needs no account) rather than silently skipping it.

Agent View of the PolicyLayer registry record for `get_dossier`. HTML page: https://policylayer.com/tools/ddmarketer-mcp/get-dossier

## Facts

- Tool: `get_dossier`
- Server: Ddmarketer (`https://www.ddmarketer.com/api/mcp`) — https://policylayer.com/tools/ddmarketer-mcp.md
- Homepage: https://github.com/CodePhantom-1/ddmarketer-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | The gap id returned by search_gaps or get_top_gaps. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_dossier",
    "arguments": {
      "id": "<id>"
    }
  }
}
```

## Why get_dossier is rated Low

Even though get_dossier 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 get_dossier to retrieve information from Ddmarketer 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 Ddmarketer:

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

## Other tools on Ddmarketer (3)

- `get_top_gaps` — Read — https://policylayer.com/tools/ddmarketer-mcp/get-top-gaps.md
- `search_gaps` — Read — https://policylayer.com/tools/ddmarketer-mcp/search-gaps.md
- `validate_idea` — Read — https://policylayer.com/tools/ddmarketer-mcp/validate-idea.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=ddmarketer-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ddmarketer-mcp
