qd_run_page

THE RISK

High Risk

Why qd_run_page needs a policy

The name 'qd_run_page' strongly implies executing or running a page, likely triggering a query or operation on the QuantData platform. Given sibling tools that create, delete, and manage pages and filter groups, 'run_page' likely executes the configured page/query against live market data. This falls under Execute. Confidence is lowered due to empty description.

From the tool's definition Tool name is 'qd_run_page'; description is empty and uninformative.

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

POLICY

How to control qd_run_page

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_run_page:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "qd_run_page": {
      "limits": [
        {
          "counter": "qd_run_page_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

qd_run_page stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. 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.

RATE-LIMIT 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 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 Write qd_add_tool_to_page qd_add_tool_to_page

All 50 QuantData MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in QuantData MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about qd_run_page

What does the qd_run_page tool do? +

qd_run_page. It is categorised as a Execute tool in the QuantData MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on qd_run_page? +

Register the QuantData MCP Server MCP server in PolicyLayer and add a rule for qd_run_page: 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_run_page? +

qd_run_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit qd_run_page? +

Yes. Add a rate_limit block to the qd_run_page 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_run_page completely? +

Set action: deny in the PolicyLayer policy for qd_run_page. 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_run_page? +

qd_run_page 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 →