Open Cainiao in a persistent browser session and return a QR/manual-login screenshot path.
AI agents invoke login_cainiao to trigger actions in Parcel Pilot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool launches a browser session (an external operation with side effects) to open the Cainiao platform and capture a screenshot. It is not a simple read — it actively starts a persistent browser process and triggers an authentication flow. This falls under Execute as it runs browser actions whose effects depend on the external service interaction.
From the tool's definition Open Cainiao in a persistent browser session and return a QR/manual-login screenshot path
Attacks that exploit this kind of access
Open Cainiao in a persistent browser session and return a QR/manual-login screenshot path. It is categorised as a Execute tool in the Parcel Pilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Parcel Pilot MCP server in PolicyLayer and add a rule for login_cainiao: 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 Parcel Pilot MCP. Nothing to install.
login_cainiao is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the login_cainiao 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 login_cainiao. 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.
login_cainiao is provided by the Parcel Pilot MCP server (jieyangxchen/parcel-pilot-mcp). 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 →