submit
One-shot submission: (optional preflight existence check) → upload the ZIP → verify the upload succeeded → publish for review → return the final status with a readable summary. Combines upload + publish + status and surfaces actionable errors at each step.
This record as markdown: /tools/1llum1n4t1-cws-mcp/submit.md
What submit does on Cws
AI agents use submit to create or update resources in Cws, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cws environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
itemId | string | — | Extension item ID (defaults to CWS_ITEM_ID env var) |
zipPath | string | Yes | Absolute path to the ZIP file to upload and submit |
preflight | boolean | — | Verify the item exists before uploading (default: true). Set false to skip the pre-check. |
skipReview | boolean | — | Attempt to skip review if the extension qualifies. Defaults to false. |
publishType | string | — | DEFAULT_PUBLISH (default): publish immediately after approval. STAGED_PUBLISH: stage for manual publishing. |
publisherId | string | — | Publisher ID (defaults to CWS_PUBLISHER_ID env var or 'me') |
blockOnWarnings | boolean | — | If true, block the publish when the submission has warnings. Defaults to false. |
deployPercentage | integer | — | Initial deploy percentage for staged rollout (0-100). |
Parameters from the server's own tool schema.
Why submit is rated Medium
An AI agent can call submit faster than any human can review: one bad instruction and it creates or modifies resources in Cws by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs submit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cws, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For submit, this is the rule to start with:
submit 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cws, apply this rule, and every submit call is checked against it from then on.
Questions about submit
One-shot submission: (optional preflight existence check) → upload the ZIP → verify the upload succeeded → publish for review → return the final status with a readable summary. Combines upload + publish + status and surfaces actionable errors at each step. It is categorised as a Write tool in the Cws MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
submit accepts 8 parameters: itemId, zipPath, preflight, skipReview, publishType, publisherId, blockOnWarnings, deployPercentage. Required: zipPath. The full parameter table on this page comes from the server's own tool schema.
Register the Cws MCP server in PolicyLayer and add a rule for submit: 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 Cws. Nothing to install.
submit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit 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.
Set action: deny in the PolicyLayer policy for submit. 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.
submit is provided by the Cws MCP server (@1llum1n4t1/cws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cws, and thousands of servers like it.
This server
Across the catalogue