Low Risk

check_service_accessibility

Real-time check: is a domain/service accessible in a specific country right now? Returns blocking status, block rate across ISPs, and evidence.

Single-target operation

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

AI agents call check_service_accessibility to retrieve information from Voidly without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though check_service_accessibility only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

voidly-mcp-server.yaml
tools:
  check_service_accessibility:
    rules:
      - action: allow

See the full Voidly policy for all 11 tools.

Tool Name check_service_accessibility
Category Read
MCP Server Voidly MCP Server
Risk Level Low

View all 11 tools →

Agents calling read-class tools like check_service_accessibility 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 Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the check_service_accessibility tool do? +

Real-time check: is a domain/service accessible in a specific country right now? Returns blocking status, block rate across ISPs, and evidence.. It is categorised as a Read tool in the Voidly MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_service_accessibility? +

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

What risk level is check_service_accessibility? +

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

Can I rate-limit check_service_accessibility? +

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

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

check_service_accessibility is provided by the Voidly MCP server (voidly/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Voidly

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.