Skip to main content
Glama
jumodada

DrissionPage MCP Server

by jumodada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Reset Browser Permissions

browser_permissions_reset
DestructiveIdempotent

Clears all Chromium permission overrides in the current browser context, restoring default permission behavior. Use it when a site's granted/denied permissions must be reset.

Instructions

Reset all Chromium permission overrides in the current browser context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tab_idNoOptional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.8.8
    • changedInput schema / description
      Previous value: -"Empty input schema for tools that don't require arguments."New value: +"Empty argument shape for a tab-scoped tool."
    • addedInput schema / properties / tab_id
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 128,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start.",
+  "title": "Tab Id"
+}
    • changedInput schema / title
      Previous value: -"EmptyInput"New value: +"TabScopedEmptyInput"
    • changedOutput schema / oneOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "data": {
-        "additionalProperties": false,
-        "properties": {
-          "context_scope": {
-            "const": "current_browser_context",
-            "title": "Context Scope",
-            "type": "string"
-          },
-          "reset": {
-            "const": true,
-            "title": "Reset",
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "reset",
-          "context_scope"
-        ],
-        "title": "BrowserPermissionsResetData",
-        "type": "object"
-      },
-      "message": {
-        "type": "string"
-      },
-      "ok": {
-        "const": true
-      }
-    },
-    "required": [
-      "ok",
-      "message",
-      "data"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "data": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "error": {
-        "additionalProperties": false,
-        "properties": {
-          "code": {
-            "type": "string"
-          },
-          "details": {
-            "additionalProperties": true,
-            "type": "object"
-          },
-          "message": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "code",
-          "message"
-        ],
-        "type": "object"
-      },
-      "message": {
-        "type": "string"
-      },
-      "ok": {
-        "const": false
-      }
-    },
-    "required": [
-      "ok",
-      "message",
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "data": {
+        "additionalProperties": false,
+        "properties": {
+          "context_scope": {
+            "const": "current_browser_context",
+            "title": "Context Scope",
+            "type": "string"
+          },
+          "reset": {
+            "const": true,
+            "title": "Reset",
+            "type": "boolean"
+          },
+          "tab_id": {
+            "description": "MCP tab id captured for this operation.",
+            "maxLength": 128,
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "reset",
+          "context_scope",
+          "tab_id"
+        ],
+        "title": "BrowserPermissionsResetData",
+        "type": "object"
+      },
+      "message": {
+        "type": "string"
+      },
+      "ok": {
+        "const": true
+      }
+    },
+    "required": [
+      "ok",
+      "message",
+      "data"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "data": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "error": {
+        "additionalProperties": false,
+        "properties": {
+          "code": {
+            "type": "string"
+          },
+          "details": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "message": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "code",
+          "message"
+        ],
+        "type": "object"
+      },
+      "message": {
+        "type": "string"
+      },
+      "ok": {
+        "const": false
+      }
+    },
+    "required": [
+      "ok",
+      "message",
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Addedv0.8.0

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the meaningful detail that the reset clears *all* overrides (not a single permission), but says nothing about reversibility, which permissions are affected, or the tab-scoped nature of the effect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero waste; the scope of the operation ('all ... overrides') leads the statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and annotations cover the destructive/idempotent profile. However, for a destructive bulk reset the description is thin: it does not say the effect is limited to the current tab, nor what state the permissions revert to, leaving gaps an agent would want before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single optional tab_id is fully documented in the schema, so the baseline is 3. The description adds nothing about tab scoping beyond implying the 'current browser context'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear specific verb+resource: 'Reset all Chromium permission overrides' names the operation and scope precisely. It is distinguishable from siblings like browser_permission_set/get in spirit, but the description never names those alternatives, so the differentiation is only inferable from the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no mention of alternatives such as browser_permission_set (which changes a single permission) versus this bulk reset. The agent is left to infer the routing from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools