ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Tool Permission Boundary Enforcer with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Enforces deterministic permission boundaries for capability execution to prevent unbounded access.

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 3 capabilities

The complete Tool Permission Boundary Enforcer capability set.

These are the exact actions your AI can choose when you ask it to work with Tool Permission Boundary Enforcer.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through Tool Permission Boundary Enforcer.

  1. 01

    Check permission

    Determines if a specific capability operation is permitted under current boundary rules

  2. 02

    List boundaries

    Retrieves the current active permission boundaries for inspection

  3. 03

    Validate resource pattern

    Tests a specific resource string against the regex or exact match rules of a given capability/operation pair

Observed, not estimated

811ms average. Fast in production.

Tool Permission Boundary Enforcer is checked daily against the live service.

Daily averagePeak 1003ms
Aug 20Today
Fastest day
668ms
Slowest day
1003ms
14-day trend
Slowing+18%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Tool Permission Boundary Enforcer, so you can see the experience inside your AI.

It does not authenticate your account with Tool Permission Boundary Enforcer. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Tool Permission Boundary Enforcer Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_GVlIoKIoNH1tQbGGKEnb5jAQ4QFvgGdB2BZv3GPD/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Tool Permission Boundary Enforcer capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "tool-permission-boundary-enforcer-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_GVlIoKIoNH1tQbGGKEnb5jAQ4QFvgGdB2BZv3GPD/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Tool Permission Boundary Enforcer owners ask.

  • 01

    How does the enforcer prevent unauthorized capability access?

    It uses check_permission to validate every requested operation against a predefined permission matrix. If the operation or the target resource does not match the allowed patterns, the request is blocked.

  • 02

    Can I see what capabilities are currently restricted?

    Yes, you can use the list_boundaries capability to retrieve the current active permission boundaries and inspect the allowed operations and patterns.

  • 03

    How do I test a path before using it?

    You can use validate_resource_pattern to test a specific resource string against the regex or exact match rules of a capability/operation pair without actually executing the capability.