novada_proxy_status

Check proxy connectivity and provider health. Returns structured JSON with ok, data.connectivity.status (HEALTHY/DEGRADED/UNAVAILABLE) and data.connectivity.proxy_ip (verified via live proxy call).\n\nWHEN TO USE: Before starting a large scraping workflow, or to diagnose proxy failures.\nNOTE: Li...

Server Novada Proxy novadalabs/novada-proxy
Category Read
Risk class Low
Parameters 00 required

What novada_proxy_status does on Novada Proxy

AI agents call novada_proxy_status to retrieve information from Novada Proxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why novada_proxy_status needs a policy

novada_proxy_status performs a diagnostic health check that queries proxy status and makes a single GET request to httpbin.org/ip for verification. This is a read-only operation that retrieves status information without modifying, deleting, or executing arbitrary code. The tool is explicitly designed for diagnostic purposes before workflows begin.

From the tool's definition Tool description states it 'Check[s] proxy connectivity and provider health. Returns structured JSON' with connectivity status. Makes 'one proxy request to httpbin.org/ip on every call' for health verification.

Questions about novada_proxy_status

What does the novada_proxy_status tool do? +

Check proxy connectivity and provider health. Returns structured JSON with ok, data.connectivity.status (HEALTHY/DEGRADED/UNAVAILABLE) and data.connectivity.proxy_ip (verified via live proxy call).\n\nWHEN TO USE: Before starting a large scraping workflow, or to diagnose proxy failures.\nNOTE: Live connectivity check — makes one proxy request to httpbin.org/ip on every call.\nUSE novada_proxy_fetch INSTEAD IF: You need to test fetching a specific URL, not general proxy health.\nON FAILURE: If PROVIDER_NOT_CONFIGURED → set proxy credentials env vars. If UNAVAILABLE → check provider dashboard. It is categorised as a Read tool in the Novada Proxy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on novada_proxy_status? +

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

What risk level is novada_proxy_status? +

novada_proxy_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit novada_proxy_status? +

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

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

novada_proxy_status is provided by the Novada Proxy MCP server (novadalabs/novada-proxy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.