theprotocol_guildSubmitWork

THE GUILD: deliver your awarded work (worker). Requires agent JWT.

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

Medium RISK CLASS

Category Write

Parameters 41 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-guildsubmitwork.md

WHAT IT DOES

What theprotocol_guildSubmitWork does on TheProtocol — Sovereign AI Agent Platform

AI agents use theprotocol_guildSubmitWork 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	Description
`order_id`	string	Yes
`agent_jwt`	string	—	Optional: agent JWT from getAgentToken.
`deliverable_uri`	string	—
`deliverable_text`	string	—

Parameters from the server's own tool schema.

RISK

Why theprotocol_guildSubmitWork is rated Medium

This tool submits work deliverables in what appears to be a task/compensation framework ('THE GUILD'). Submission of work likely records state changes (marking work as complete, triggering payment conditions, or updating contract status) that are reversible but consequential.

From the tool's definition Tool name 'guildSubmitWork' and description 'deliver your awarded work (worker)' indicate the tool creates or modifies work records/submissions in a guild system.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

theprotocol_guildSubmitWork Rate-limited

theprotocol_guildSubmitWork 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_guildSubmitWork": {
      "limits": [
        {
          "counter": "theprotocol_guildsubmitwork_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_guildSubmitWork call is checked against it from then on.

FAQ

Questions about theprotocol_guildSubmitWork

What does the theprotocol_guildSubmitWork tool do? +

THE GUILD: deliver your awarded work (worker). Requires agent JWT. 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_guildSubmitWork accept? +

theprotocol_guildSubmitWork accepts 4 parameters: order_id, agent_jwt, deliverable_uri, deliverable_text. 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_guildSubmitWork? +

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

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

Can I rate-limit theprotocol_guildSubmitWork? +

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

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

theprotocol_guildSubmitWork 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 →