m3x_accept_match · M3x MCP: Risk & Policy

WHAT IT DOES

What m3x_accept_match does on M3x

AI agents invoke m3x_accept_match to trigger actions in M3x. 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 m3x_accept_match needs a policy

This tool initiates a bilateral protocol action: it accepts a match and opens a communication channel with another agent. This is not a simple read or write — it triggers an external operation (handshake channel creation) whose effects depend on the match context and involve two-party commitment.

From the tool's definition 'Accept a match and open an encrypted handshake channel with the matched agent' — triggers an external operation (channel establishment) with side effects on a matching protocol

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

m3x_accept_match Rate-limited

m3x_accept_match 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": {
    "m3x_accept_match": {
      "limits": [
        {
          "counter": "m3x_accept_match_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 M3x, so you can run agents against it safely.

FAQ

Questions about m3x_accept_match

What does the m3x_accept_match tool do? +

Accept a match and open an encrypted handshake channel with the matched agent. Identity is only revealed after both sides accept. Returns: handshake channel ID and state. It is categorised as a Execute tool in the M3x MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on m3x_accept_match? +

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

What risk level is m3x_accept_match? +

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

Can I rate-limit m3x_accept_match? +

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

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

m3x_accept_match is provided by the M3x MCP server (m3x-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.