Low Risk

qd_add_or_branch

qd_add_or_branch

How to control qd_add_or_branch ↓

What qd_add_or_branch does on QuantData MCP Server

AI agents call qd_add_or_branch as a supporting operation in QuantData MCP Server workflows.

Low Risk

Why qd_add_or_branch needs a policy

With no description available, classification relies solely on the name. 'qd_add_or_branch' likely adds an OR logical branch to a filter query structure (a Write/configuration action), based on sibling tools like qd_add_filter_clause and qd_apply_filter_group. Confidence is very low due to lack of description. Defaulting to Other given insufficient evidence, though Write is plausible.

From the tool's definition Tool description is empty and uninformative; tool name 'qd_add_or_branch' suggests adding a logical OR branch to a filter, which would be a Write operation, but this cannot be confirmed.

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

How to control qd_add_or_branch

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "qd_add_or_branch": {
      "limits": [
        {
          "counter": "qd_add_or_branch_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

qd_add_or_branch gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register QuantData MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about qd_add_or_branch

What does the qd_add_or_branch tool do? +

qd_add_or_branch. It is categorised as a Other tool in the QuantData MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on qd_add_or_branch? +

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

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

Can I rate-limit qd_add_or_branch? +

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

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

qd_add_or_branch 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.

Free to start. No card required.

50 QuantData MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.