qd_list_pages

THE RISK

Low Risk

Why qd_list_pages needs a policy

This tool retrieves configuration metadata (list of saved pages) without modifying, executing, or deleting anything. It has minimal blast radius if misused by an AI agent—the worst outcome is information disclosure of page names/configurations already accessible to the authenticated user. This is a straightforward read/query operation.

From the tool's definition Tool name 'qd_list_pages' and description 'List the user-managed pages saved to the MCP config' indicate a retrieval operation with no side effects. The verb 'list' is a read-only query operation.

Documented attack patterns abuse exactly the kind of access qd_list_pages gives an agent:

POLICY

How to control qd_list_pages

PolicyLayer is an MCP gateway — it sits between your AI agents and QuantData MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for qd_list_pages:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "qd_list_pages": {}
  }
}

qd_list_pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register QuantData MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More QuantData MCP Server tools

Destructive qd_delete_filter_group Delete a filter group permanently. Detaches it from any tools that Destructive qd_delete_page qd_delete_page Destructive qd_remove_filter_clause qd_remove_filter_clause Execute qd_run_page qd_run_page Write qd_detach_filter_group Remove a previously-attached filter group from a tool. Idempotent. Write qd_reset_to_live Remove the time scrubber from a tool — return it to live mode. Write qd_clone_public_filter_group qd_clone_public_filter_group Write qd_add_filter_clause qd_add_filter_clause

All 50 QuantData MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about qd_list_pages

What does the qd_list_pages tool do? +

List the user-managed pages saved to the MCP config. It is categorised as a Read tool in the QuantData MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on qd_list_pages? +

Register the QuantData MCP Server MCP server in PolicyLayer and add a rule for qd_list_pages: 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 QuantData MCP Server. Nothing to install.

What risk level is qd_list_pages? +

qd_list_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit qd_list_pages? +

Yes. Add a rate_limit block to the qd_list_pages 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.

How do I block qd_list_pages completely? +

Set action: deny in the PolicyLayer policy for qd_list_pages. 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.

What MCP server provides qd_list_pages? +

qd_list_pages is provided by the QuantData MCP Server MCP server (zzulanas/quantdata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every QuantData MCP Server tool call.

Start from QuantData MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →