meshes_create_connection · Mesheshq MCP: Risk & Policy

WHAT IT DOES

What meshes_create_connection does on Mesheshq

AI agents use meshes_create_connection to create or update resources in Mesheshq — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mesheshq environment.

WHY IT NEEDS A POLICY

Why meshes_create_connection needs a policy

This tool creates new integration connections with sensitive configuration data (API keys, OAuth tokens, webhooks). While it is reversible (connections can be deleted via meshes_delete_connection), it establishes external integrations that could expose credentials or enable unauthorized data flows if misconfigured by a compromised agent.

From the tool's definition Tool description states 'Create a new connection' and 'metadata object contains connector-specific configuration (API keys, OAuth tokens, webhook URLs, etc.)'. The 'create' action and handling of sensitive credentials indicate data creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

meshes_create_connection Rate-limited

meshes_create_connection stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "meshes_create_connection": {
      "limits": [
        {
          "counter": "meshes_create_connection_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about meshes_create_connection

What does the meshes_create_connection tool do? +

Create a new connection (destination) in a workspace. The metadata object contains connector-specific configuration (API keys, OAuth tokens, webhook URLs, etc.). It is categorised as a Write tool in the Mesheshq MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on meshes_create_connection? +

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

What risk level is meshes_create_connection? +

meshes_create_connection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit meshes_create_connection? +

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

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

meshes_create_connection is provided by the Mesheshq MCP server (mesheshq/meshes-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.