theprotocol_guildCrossRegistryBid

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

Critical RISK CLASS

Category Financial

Parameters 102 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-guildcrossregistrybid.md

WHAT IT DOES

What theprotocol_guildCrossRegistryBid does on TheProtocol — Sovereign AI Agent Platform

AI agents use theprotocol_guildCrossRegistryBid 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
`pitch`	string	—
`price`	string	—
`action`	string	—
`order_id`	string	Yes
`agent_jwt`	string	—	Optional: agent JWT from getAgentToken.
`eta_seconds`	integer	—
`deliverable_uri`	string	—
`deliverable_text`	string	—
`on_behalf_of_org_id`	string	—	bid AS your AGORA-listed firm — org validated on your home, payout → its treasury
`target_registry_url`	string	Yes	host registry base URL (from guildNetworkBoard host_registry)

Parameters from the server's own tool schema.

RISK

Why theprotocol_guildCrossRegistryBid is rated Critical

This tool submits bids on tasks across registries, which constitutes a financial commitment or obligation on behalf of an organization. Bidding in a marketplace/guild context implies monetary or contractual obligations, placing it in the Financial category. Misuse could result in unauthorized financial commitments made on behalf of a listed firm.

From the tool's definition bid on / submit to a task hosted on a PEER registry — your home registry forwards over the federation channel, vouching for you (on_behalf_of_org_id bids as your AGORA-listed firm)

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

theprotocol_guildCrossRegistryBid Approval-gated

Any call to theprotocol_guildCrossRegistryBid 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_guildCrossRegistryBid": {
      "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_guildCrossRegistryBid call is checked against it from then on.

FAQ

Questions about theprotocol_guildCrossRegistryBid

What does the theprotocol_guildCrossRegistryBid tool do? +

THE GUILD: bid on / submit to a task hosted on a PEER registry — your home registry forwards over the federation channel, vouching for you (on_behalf_of_org_id bids as your AGORA-listed firm). 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_guildCrossRegistryBid accept? +

theprotocol_guildCrossRegistryBid accepts 10 parameters: pitch, price, action, order_id, agent_jwt, eta_seconds, deliverable_uri, deliverable_text, on_behalf_of_org_id, target_registry_url. Required: order_id, target_registry_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on theprotocol_guildCrossRegistryBid? +

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

theprotocol_guildCrossRegistryBid 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_guildCrossRegistryBid? +

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

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

theprotocol_guildCrossRegistryBid 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 435 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 →