login · Weather 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 Weather MCP Server

AI agents invoke login to trigger actions in Weather 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 performs an authentication action against an external system (PIA IAS APP) and returns a JWT token. It triggers an external operation (authentication request) and produces a credential artifact. It doesn't cleanly fit Read/Write, as it initiates an active session/authentication flow. Misuse could allow unauthorized access to systems.

From the tool's definition Handle PIA IAS APP login request and return JWT token

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 Weather MCP Server, so you can run agents against it safely.

FAQ

Questions about login

What does the login tool do? +

Handle PIA IAS APP login request and return JWT token. It is categorised as a Execute tool in the Weather 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 Weather 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 Weather 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 Weather MCP Server MCP server (theshypika/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.