AI agents invoke monitoring_uptime_check to trigger actions in Infra Ops. 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 performs active network probing by initiating HTTP or TCP connections to specified targets. While it is primarily a read/monitoring operation, it executes outbound network requests whose effects depend on arguments (target host, port, protocol). A misconfigured or malicious argument could direct the server to probe internal infrastructure, sensitive endpoints, or act as a basic SSRF vector.
From the tool's definition 'Perform an HTTP or TCP uptime check on a target' — actively initiates network connections (HTTP or TCP) to external targets
Attacks that exploit this kind of access
Perform an HTTP or TCP uptime check on a target. It is categorised as a Execute tool in the Infra Ops MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Infra Ops MCP server in PolicyLayer and add a rule for monitoring_uptime_check: 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 Infra Ops. Nothing to install.
monitoring_uptime_check 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 monitoring_uptime_check 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 monitoring_uptime_check. 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.
monitoring_uptime_check is provided by the Infra Ops MCP server (skyvanguard/infra-ops-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 →