check_browser_availability · GitHub-Jira MCP Server MCP

WHAT IT DOES

What check_browser_availability does on GitHub-Jira MCP Server

AI agents call check_browser_availability as a supporting operation in GitHub-Jira MCP Server workflows.

WHY IT NEEDS A POLICY

Why check_browser_availability needs a policy

With no description available, classification is uncertain. The name suggests checking whether a browser is available (a read/status operation with no side effects), but this is speculative. Given the server context (GitHub/Jira integration), this tool seems anomalous. Confidence is low due to the empty description.

From the tool's definition Tool description is empty and uninformative; the tool name 'check_browser_availability' does not match any sibling tools and suggests a read/status check operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

check_browser_availability Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_browser_availability": {
      "limits": [
        {
          "counter": "check_browser_availability_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitHub-Jira MCP Server, so you can run agents against it safely.

FAQ

Questions about check_browser_availability

What does the check_browser_availability tool do? +

check_browser_availability. It is categorised as a Other tool in the GitHub-Jira MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on check_browser_availability? +

Register the GitHub-Jira MCP Server MCP server in PolicyLayer and add a rule for check_browser_availability: 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 GitHub-Jira MCP Server. Nothing to install.

What risk level is check_browser_availability? +

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

Can I rate-limit check_browser_availability? +

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

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

check_browser_availability is provided by the GitHub-Jira MCP Server MCP server (kronoswastaken/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.