Find-or-create a Shipeasy project by domain (idempotent) and bind the cwd to it via .shipeasy. Use this on fresh installs BEFORE any other write tool — every other write tool refuses to run until .shipeasy exists. Re-running with the same domain returns the existing project unchanged.
AI agents use projects_upsert to create or update resources in Shipeasy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shipeasy environment.
This tool creates new resources (projects) and modifies the local filesystem by writing a .shipeasy configuration file. These are reversible write operations. It's not Execute because it doesn't run arbitrary code or scripts. It's not Destructive because the operations are reversible (the .shipeasy file can be deleted, project creation is idempotent).
From the tool's definition Tool performs 'find-or-create' operation and 'bind' action, modifying state by creating .shipeasy configuration file. Description explicitly states it creates projects and writes configuration.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Find-or-create a Shipeasy project by domain (idempotent) and bind the cwd to it via .shipeasy. Use this on fresh installs BEFORE any other write tool — every other write tool refuses to run until .shipeasy exists. Re-running with the same domain returns the existing project unchanged. It is categorised as a Write tool in the Shipeasy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shipeasy MCP server in PolicyLayer and add a rule for projects_upsert: 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 Shipeasy. Nothing to install.
projects_upsert 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 projects_upsert 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 projects_upsert. 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.
projects_upsert is provided by the Shipeasy MCP server (shipeasy-ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
projects_upsert is one line of Shipeasy's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →