complete_browser_auth · Meducate MCP: Risk & Policy

WHAT IT DOES

What complete_browser_auth does on Meducate MCP

AI agents invoke complete_browser_auth to trigger actions in Meducate MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why complete_browser_auth needs a policy

This tool executes an OAuth authentication flow using a one-time code, completing a browser-based authorization process. This is an Execute-category action because it triggers an external authentication operation with real side effects (establishing an authenticated session/token).

From the tool's definition Complete the browser-based OAuth flow with a one-time code

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_browser_auth Rate-limited

complete_browser_auth stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "complete_browser_auth": {
      "limits": [
        {
          "counter": "complete_browser_auth_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about complete_browser_auth

What does the complete_browser_auth tool do? +

Complete the browser-based OAuth flow with a one-time code. It is categorised as a Execute tool in the Meducate MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on complete_browser_auth? +

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

What risk level is complete_browser_auth? +

complete_browser_auth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit complete_browser_auth? +

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

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

complete_browser_auth is provided by the Meducate MCP server (joshnuku/meducate-mcp-demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.