check_vector

Check Vector (log pipeline) reachability via GET /health. Default port 8686. Returns healthy status and component details from health response.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-vector.md

WHAT IT DOES

What check_vector does on Mcp Nettools

AI agents call check_vector to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_vector is rated Low

This tool retrieves diagnostic information from a Vector instance using a simple HTTP GET request to a health endpoint. It only reads and reports status data without creating, modifying, deleting, or executing anything. The health check is a standard, non-invasive network diagnostic operation with minimal blast radius if misused.

From the tool's definition Tool description states it performs a GET /health check, which is a read-only query operation. It 'Returns healthy status and component details from health response' with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_vector safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_vector, this is the rule to start with:

check_vector Allowed

check_vector is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_vector call is checked against it from then on.

FAQ

Questions about check_vector

What does the check_vector tool do? +

Check Vector (log pipeline) reachability via GET /health. Default port 8686. Returns healthy status and component details from health response. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_vector? +

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

What risk level is check_vector? +

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

Can I rate-limit check_vector? +

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

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

check_vector is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

vector_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →