login · PingCode MCP Server MCP: Risk & Policy

Q: What risk level is login?

login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

WHAT IT DOES

What login does on PingCode MCP Server

AI agents invoke login to trigger actions in PingCode MCP Server. 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.

WHY IT NEEDS A POLICY

Why login needs a policy

This tool opens a browser to perform a login flow and automatically saves credentials upon success. It triggers an external browser action and persists authentication state, which qualifies as Execute (browser action with side effects). Misuse could lead to credential capture or unauthorized session establishment.

From the tool's definition 打开浏览器进行 PingCode 登录（支持飞书等第三方登录）。登录成功后凭证会自动保存。

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

login stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "login": {
      "limits": [
        {
          "counter": "login_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PingCode MCP Server, so you can run agents against it safely.

FAQ

Questions about login

What does the login tool do? +

打开浏览器进行 PingCode 登录（支持飞书等第三方登录）。登录成功后凭证会自动保存。. It is categorised as a Execute tool in the PingCode MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on login? +

Register the PingCode MCP Server MCP server in PolicyLayer and add a rule for login: 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 PingCode MCP Server. Nothing to install.

What risk level is login? +

Can I rate-limit login? +

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

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

login is provided by the PingCode MCP Server MCP server (ratatatat1/pingcode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.