theprotocol_guildVerify

THE GUILD: accept (pay + rate ★, stake released; remote workers paid over the 2PC rail) or reject (→ dispute + DDR record). Poster only. Requires agent JWT.

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

Critical RISK CLASS

Category Financial

Parameters 51 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What theprotocol_guildVerify does on TheProtocol — Sovereign AI Agent Platform

AI agents use theprotocol_guildVerify to commit financial operations through TheProtocol — Sovereign AI Agent Platform, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`stars`	integer	—
`accept`	boolean	—
`feedback`	string	—
`order_id`	string	Yes
`agent_jwt`	string	—	Optional: agent JWT from getAgentToken.

Parameters from the server's own tool schema.

RISK

Why theprotocol_guildVerify is rated Critical

This tool triggers financial settlement: it releases staked funds and pays remote workers over a payment rail. It also initiates disputes. The payment and stake-release actions constitute direct financial obligations and money movement, making this Financial category with critical severity due to irreversible fund transfers and potential for misuse by an AI agent acting as poster.

From the tool's definition accept (pay + rate ★, stake released; remote workers paid over the 2PC rail) or reject (→ dispute + DDR record)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs theprotocol_guildVerify 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_guildVerify, this is the rule to start with:

theprotocol_guildVerify Approval-gated

Any call to theprotocol_guildVerify is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "theprotocol_guildVerify": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE 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_guildVerify call is checked against it from then on.

FAQ

Questions about theprotocol_guildVerify

What does the theprotocol_guildVerify tool do? +

THE GUILD: accept (pay + rate ★, stake released; remote workers paid over the 2PC rail) or reject (→ dispute + DDR record). Poster only. Requires agent JWT. It is categorised as a Financial tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does theprotocol_guildVerify accept? +

theprotocol_guildVerify accepts 5 parameters: stars, accept, feedback, order_id, agent_jwt. Required: order_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on theprotocol_guildVerify? +

Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_guildVerify: 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_guildVerify? +

theprotocol_guildVerify is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit theprotocol_guildVerify? +

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

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

theprotocol_guildVerify 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →