Uploads a new version of a miniprogram project from the specified path. Requires a version number and a description for the upload.
AI agents use uploadMiniprogram to create or update resources in Tcsas Devtools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tcsas Devtools environment.
This tool pushes a new version of a miniprogram to a platform/service, which is a write/publish operation. While it creates a new version (reversible in the sense that old versions may remain), uploading to a production or staging environment can have significant impact if misused — wrong version, wrong code, etc.
From the tool's definition Uploads a new version of a miniprogram project from the specified path. Requires a version number and a description for the upload.
Attacks that exploit this kind of access
Uploads a new version of a miniprogram project from the specified path. Requires a version number and a description for the upload. It is categorised as a Write tool in the Tcsas Devtools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tcsas Devtools MCP server in PolicyLayer and add a rule for uploadMiniprogram: 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 Tcsas Devtools. Nothing to install.
uploadMiniprogram 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 uploadMiniprogram 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 uploadMiniprogram. 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.
uploadMiniprogram is provided by the Tcsas Devtools MCP server (tcmpp-team/tcsas-devtools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →