agent-browser-mcp

Overview Schema Source Related Servers Discussions Admin

set_site_permission

Destructive

Set a temporary browser permission for a specific origin, such as notifications or geolocation, and automatically restore the prior setting after a chosen duration.

Instructions

Temporarily set an origin-scoped browser site permission for 60-600 seconds. Only http/https origins and notifications, geolocation/location, camera or microphone are supported; clipboard returns unsupported because its prior state cannot be restored. safe asks on every allow; lab skips prompts by default and restores session approval only when BROWSERTAP_LAB_NO_ELICIT is explicitly disabled. Leases attempt to restore their prior setting. requires_user_action.reason distinguishes elicitation_unsupported, declined, timeout, cancelled and error; an unsuccessful approval never sends a permission grant. If restoration becomes unsupported, manual_recovery retains that setting and recovery guidance without automatic retries; an explicit reset can retry after the cause is resolved.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "permission": "<permission>",
      "setting": "<setting>"
    },
    "name": "set_site_permission"
  }
}

Input Schema

Name	Required	Description	Default
`origin`	No
`setting`	Yes
`permission`	Yes
`session_id`	No
`duration_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already mark the operation as destructive and non-idempotent, and the description adds substantial context: restoration attempts, mode-dependent prompt behavior, requires_user_action.reason values, no grant on unsuccessful approval, and manual_recovery semantics. No contradiction with annotations exists.

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

Conciseness4/5

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

The first sentence front-loads the core purpose, and later sentences provide useful edge-case details not inferable from schema or annotations. The paragraph is dense and a bit run-on, but every sentence contributes meaningful behavioral information.

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?

For a destructive, non-idempotent operation with no parameter descriptions in the schema, the description covers supported inputs, failure reasons, and recovery semantics well. However, the required 'setting' parameter and 'session_id' remain undefined, so an agent cannot fully construct a valid call from the description alone.

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?

With 0% schema description coverage, the description must explain parameters itself. It clarifies origin (http/https only), permission (supported list, clipboard exception), and duration_seconds (60-600). However, the required 'setting' parameter is never given its possible values, and 'session_id' is left unexplained, so parameter meaning is only partially compensated.

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

Purpose5/5

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

The opening sentence states a specific verb (set), resource (browser site permission), scope (origin), and time bound (60-600 seconds). It also clearly distinguishes this temporary, lease-like operation from the sibling reset_site_permissions tool.

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

Usage Guidelines4/5

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

The description gives concrete eligibility rules: only http/https origins and a specific set of permissions are supported; clipboard is explicitly excluded. It also describes safe vs. lab mode behavior and mentions reset as the recovery path, providing clear context for when this tool applies, though it does not name a direct alternative for permanent permission removal.

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

Deploy Server