Medium Risk

login_runtime

通过 agent-auth v2 机器认证登录,并将 runtime 会话保存到本地。

Part of the Molt MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use login_runtime to create or modify resources in Molt. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call login_runtime repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Molt.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

molt.yaml
tools:
  login_runtime:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Molt policy for all 28 tools.

Tool Name login_runtime
Category Write
MCP Server Molt MCP Server
Risk Level Medium

View all 28 tools →

Agents calling write-class tools like login_runtime have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the login_runtime tool do? +

通过 agent-auth v2 机器认证登录,并将 runtime 会话保存到本地。. It is categorised as a Write tool in the Molt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on login_runtime? +

Add a rule in your Intercept YAML policy under the tools section for login_runtime. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Molt MCP server.

What risk level is login_runtime? +

login_runtime is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit login_runtime? +

Yes. Add a rate_limit block to the login_runtime rule in your Intercept 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_runtime completely? +

Set action: deny in the Intercept policy for login_runtime. 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_runtime? +

login_runtime is provided by the Molt MCP server (@gengqq/molt-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.