client_status

THE RISK

Low Risk

Why client_status needs a policy

This tool retrieves connection status information about WebSocket clients. It performs no mutations, executions, deletions, or financial transactions. The operation is read-only and has minimal blast radius—knowing if a client is connected cannot cause harm through misuse.

From the tool's definition Tool name is 'client_status' and description states 'Check if there is a client connected via WebSocket' — this is a query/check operation that retrieves status information without modifying any state or triggering external operations.

Documented attack patterns abuse exactly the kind of access client_status gives an agent:

POLICY

How to control client_status

PolicyLayer is an MCP gateway — it sits between your AI agents and React Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for client_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "client_status": {}
  }
}

client_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register React Tools — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More React Tools tools

Execute app_navigate List available routes or navigate to a path in the app. Call without Execute admin_action Perform admin action Execute validate_form Run validation on the current form state and return all errors Write fill_field Fill a specific form field with a value. Write submit_form Validate and submit the registration form. Returns validation errors if form is invalid, o Read get_click_events Get user click events Read get_field_info Get detailed information about a specific form field Read get_form_analytics Get analytics and statistics about the form state

All 20 React Tools tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about client_status

What does the client_status tool do? +

Check if there is a client connected via WebSocket. It is categorised as a Read tool in the React Tools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on client_status? +

Register the React Tools MCP server in PolicyLayer and add a rule for client_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 React Tools. Nothing to install.

What risk level is client_status? +

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

Can I rate-limit client_status? +

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

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

client_status is provided by the React Tools MCP server (mcp-fe/mcp-fe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every React Tools tool call.

Start from React Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →