uxi_list_sensors

List UXI sensors with compact identity, model, MAC, group, and location fields.

SERVERHpe Networking SOURCEsecure-ssid/hpe-networking-mcp

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/hpe-networking-mcp/uxi-list-sensors.md

WHAT IT DOES

What uxi_list_sensors does on Hpe Networking

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

RISK

Why uxi_list_sensors is rated Low

This tool performs a query/list operation that retrieves existing sensor metadata. It has no side effects, creates no data, executes no commands, modifies nothing, and incurs no financial impact. The verb 'List' and the focus on reading sensor fields (identity, model, MAC, group, location) confirm this is a Read category tool with low severity.

From the tool's definition Tool name 'uxi_list_sensors' and description 'List UXI sensors with compact identity, model, MAC, group, and location fields' indicate a retrieval operation that returns sensor information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs uxi_list_sensors safely

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

uxi_list_sensors Allowed

uxi_list_sensors 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": {
    "uxi_list_sensors": {}
  }
}

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

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

FAQ

Questions about uxi_list_sensors

What does the uxi_list_sensors tool do? +

List UXI sensors with compact identity, model, MAC, group, and location fields. It is categorised as a Read tool in the Hpe Networking MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on uxi_list_sensors? +

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

What risk level is uxi_list_sensors? +

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

Can I rate-limit uxi_list_sensors? +

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

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

uxi_list_sensors is provided by the Hpe Networking MCP server (secure-ssid/hpe-networking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hpe Networking, and thousands of servers like it.

This server

All 595 Hpe Networking tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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