theprotocol_createFrameInvitation

DESTRUCTIVE: initiate cross-frame federation handshake. Sovereign-mainframe-only.

SERVERTheProtocol — Sovereign AI Agent Platform SOURCEhttps://api.theprotocol.cloud/mcp/sse

Medium RISK CLASS

Category Write

Parameters 86 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-createframeinvitation.md

WHAT IT DOES

What theprotocol_createFrameInvitation does on TheProtocol — Sovereign AI Agent Platform

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

Parameter	Type	Required
`name`	string	Yes
`description`	string	—
`trust_domain`	string	Yes
`contact_email`	string	Yes
`event_store_url`	string	—
`initiator_nonce`	string	Yes
`bundle_endpoint_url`	string	Yes
`federation_endpoint_url`	string	Yes

Parameters from the server's own tool schema.

RISK

Why theprotocol_createFrameInvitation is rated Medium

The tool creates/initiates a new federation request between frames rather than deleting or permanently destroying data. While marked DESTRUCTIVE in the description, the actual operation described—initiating a handshake—is a reversible write action. However, it operates on a sovereign platform with potentially significant trust/access implications, warranting high severity.

From the tool's definition Tool description states 'initiate cross-frame federation handshake' which is a write/creation operation. The description is labeled 'DESTRUCTIVE' but this appears to be a misnomer—creating a federation handshake request is reversible (can be…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs theprotocol_createFrameInvitation safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TheProtocol — Sovereign AI Agent Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For theprotocol_createFrameInvitation, this is the rule to start with:

theprotocol_createFrameInvitation Rate-limited

theprotocol_createFrameInvitation 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": {
    "theprotocol_createFrameInvitation": {
      "limits": [
        {
          "counter": "theprotocol_createframeinvitation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_createFrameInvitation call is checked against it from then on.

FAQ

Questions about theprotocol_createFrameInvitation

What does the theprotocol_createFrameInvitation tool do? +

DESTRUCTIVE: initiate cross-frame federation handshake. Sovereign-mainframe-only. It is categorised as a Write tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does theprotocol_createFrameInvitation accept? +

theprotocol_createFrameInvitation accepts 8 parameters: name, description, trust_domain, contact_email, event_store_url, initiator_nonce, bundle_endpoint_url, federation_endpoint_url. Required: name, trust_domain, contact_email, initiator_nonce, bundle_endpoint_url, federation_endpoint_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on theprotocol_createFrameInvitation? +

Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_createFrameInvitation: 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 TheProtocol — Sovereign AI Agent Platform. Nothing to install.

What risk level is theprotocol_createFrameInvitation? +

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

Can I rate-limit theprotocol_createFrameInvitation? +

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

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

theprotocol_createFrameInvitation is provided by the TheProtocol — Sovereign AI Agent Platform MCP server (https://api.theprotocol.cloud/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.

This server

All 413 TheProtocol — Sovereign AI Agent Platform tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →