Low Risk

is_service_down

Check if a specific AI service is currently down or experiencing issues.

Single-target operation

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

AI agents call is_service_down to retrieve information from TensorFeed 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 is_service_down 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.

tensorfeed.yaml
tools:
  is_service_down:
    rules:
      - action: allow

See the full TensorFeed policy for all 42 tools.

Tool Name is_service_down
Category Read
Risk Level Low

View all 42 tools →

Agents calling read-class tools like is_service_down 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 is_service_down tool do? +

Check if a specific AI service is currently down or experiencing issues.. It is categorised as a Read tool in the TensorFeed MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on is_service_down? +

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

What risk level is is_service_down? +

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

Can I rate-limit is_service_down? +

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

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

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

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.