Log in to an existing PingZen account. Returns access token, refresh token, and a permanent API key. After login, all other tools become available. The API key (pz_...) never expires — save it for permanent MCP access. Common use cases: - 'Log me in to PingZen' - 'I already have an account' Re...
Handles credentials or secrets (password)
Part of the PingZen Uptime Monitoring MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use login to create or modify resources in PingZen Uptime Monitoring. 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 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 PingZen Uptime Monitoring.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
login:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full PingZen Uptime Monitoring policy for all 44 tools.
Agents calling write-class tools like login have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Log in to an existing PingZen account. Returns access token, refresh token, and a permanent API key. After login, all other tools become available. The API key (pz_...) never expires — save it for permanent MCP access. Common use cases: - 'Log me in to PingZen' - 'I already have an account' Returns: access_token, refresh_token, expires_in, user_id, api_key.. It is categorised as a Write tool in the PingZen Uptime Monitoring MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for login. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the PingZen Uptime Monitoring MCP server.
login 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 login 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.
Set action: deny in the Intercept 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.
login is provided by the PingZen Uptime Monitoring MCP server (pingzen/uptime-monitoring). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept