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 ht...
This record as markdown: /tools/ddmarketer-mcp/get-dossier.md
What get_dossier does on Ddmarketer
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.
| 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.
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.
Attacks that exploit this kind of access
The rule that runs get_dossier safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ddmarketer, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dossier, this is the rule to start with:
get_dossier is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ddmarketer, apply this rule, and every get_dossier call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Ddmarketer MCP Server, which means it retrieves data without modifying state.
get_dossier accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Ddmarketer MCP server in PolicyLayer and add a rule for get_dossier: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Ddmarketer. Nothing to install.
get_dossier is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_dossier rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_dossier. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_dossier is provided by the Ddmarketer MCP server (https://www.ddmarketer.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ddmarketer, and thousands of servers like it.
This server
Across the catalogue