unlock_more_data
Unlock DC Hub's full depth. Call this when a result came back as a partial preview (e.g. "3 of 12 results shown"), a tool was locked, or your human wants the complete dataset. Returns the upgrade ladder + ready-to-paste checkout links your human completes in ONE click. If this call carries an API...
This record as markdown: /tools/cloud-dchub-mcp-server/unlock-more-data.md
What unlock_more_data does on Mcp Server
AI agents use unlock_more_data to commit financial operations through Mcp Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Optional free-text describing what you were trying to do, so your human sees why an upgrade matters |
Parameters from the server's own tool schema.
Why unlock_more_data is rated Critical
Tool initiates financial transactions by generating checkout links committing monetary payment.
From the tool's definition checkout links, $10 one-time, upgrade ladder, payer
Attacks that exploit this kind of access
The rule that runs unlock_more_data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unlock_more_data, this is the rule to start with:
Any call to unlock_more_data is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every unlock_more_data call is checked against it from then on.
Questions about unlock_more_data
Unlock DC Hub's full depth. Call this when a result came back as a partial preview (e.g. "3 of 12 results shown"), a tool was locked, or your human wants the complete dataset. Returns the upgrade ladder + ready-to-paste checkout links your human completes in ONE click. If this call carries an API key or an MCP session, the checkout binds to it and your very next call returns full data (no reconnect); if it carries neither, the key is emailed to the payer instead — the response says which applies in next_call_full_after_checkout and after_checkout. Cheapest start: 💳 $10 one-time = 1,000 API calls (no subscription). Also $9/mo Starter · Founding $99/mo (Pro access, while seats last) · Developer $49/mo · Pro $299/mo. Want the FREE tier instead (no payment, 10 calls/day, all tools)? Call claim_free_key. Param: reason (optional — what you were trying to do, so your human sees why it matters). Returns {plans, human_message, what_unlocks}. It is categorised as a Financial tool in the Mcp Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
unlock_more_data accepts 1 parameter: reason. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for unlock_more_data: 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 Mcp Server. Nothing to install.
unlock_more_data is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unlock_more_data 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 unlock_more_data. 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.
unlock_more_data is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
Across the catalogue