macro_contact_handshake · MCP Agent Mail MCP: Risk & Policy

WHAT IT DOES

What macro_contact_handshake does on MCP Agent Mail

AI agents call macro_contact_handshake as a supporting operation in MCP Agent Mail workflows.

WHY IT NEEDS A POLICY

Why macro_contact_handshake needs a policy

With no description available, classification is uncertain. The name suggests a handshake/coordination operation between agents, which could be a Read or Write operation. Given the server's focus on agent coordination, messaging, and identity, this likely initiates or establishes communication between agents, but without a description, confidence is very low. Defaulting to Other with low severity given the ambiguity.

From the tool's definition Tool description is empty and uninformative; the name 'macro_contact_handshake' suggests some form of agent coordination or identity exchange based on server context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

macro_contact_handshake Rate-limited

macro_contact_handshake 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": {
    "macro_contact_handshake": {
      "limits": [
        {
          "counter": "macro_contact_handshake_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 MCP Agent Mail, so you can run agents against it safely.

FAQ

Questions about macro_contact_handshake

What does the macro_contact_handshake tool do? +

macro_contact_handshake. It is categorised as a Other tool in the MCP Agent Mail MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on macro_contact_handshake? +

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

What risk level is macro_contact_handshake? +

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

Can I rate-limit macro_contact_handshake? +

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

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

macro_contact_handshake is provided by the MCP Agent Mail MCP server (omelchmichael/mcp_agent_mail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.