Low Risk

mdb_push_tools

Push MCP tools to the tools stack

How to control mdb_push_tools ↓

What mdb_push_tools does on Better Playwright MCP

AI agents call mdb_push_tools as a supporting operation in Better Playwright MCP workflows.

Low Risk

Why mdb_push_tools needs a policy

This tool appears to manage the internal MCP tools stack by pushing tools onto it. It doesn't directly interact with the browser, execute code, delete data, or move money. It is a meta-operation within the MCP framework itself. The description is vague, lowering confidence.

From the tool's definition 'Push MCP tools to the tools stack' — modifies the internal tool registry/stack within the MCP server context

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

How to control mdb_push_tools

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

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

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

  1. Create a free account and register Better Playwright MCP — 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 mdb_push_tools

What does the mdb_push_tools tool do? +

Push MCP tools to the tools stack. It is categorised as a Other tool in the Better Playwright MCP MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on mdb_push_tools? +

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

What risk level is mdb_push_tools? +

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

Can I rate-limit mdb_push_tools? +

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

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

mdb_push_tools is provided by the Better Playwright MCP server (livoras/better-playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Better Playwright MCP tool call.

Start from Better Playwright MCP, 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.

29 Better Playwright MCP 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.