New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

run_speed_test

Run a speed test from an AP to measure uplink bandwidth.

SERVERHpe Networking SOURCEsecure-ssid/hpe-networking-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hpe-networking-mcp/run-speed-test.md

What run_speed_test does on Hpe Networking

AI agents invoke run_speed_test to trigger actions in Hpe Networking. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why run_speed_test is rated High

This tool executes an operation (speed test) on network infrastructure that has real-world effects: it consumes bandwidth, generates network traffic, and produces results dependent on runtime conditions. While not destructive or financial, it's an active execution of a network diagnostic command rather than a passive read.

From the tool's definition Tool description states it will 'Run a speed test from an AP' — this actively triggers an external network operation whose effects depend on which AP is targeted and when the test runs.

Questions about run_speed_test

What does the run_speed_test tool do? +

Run a speed test from an AP to measure uplink bandwidth. It is categorised as a Execute tool in the Hpe Networking MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_speed_test? +

Register the Hpe Networking MCP server in PolicyLayer and add a rule for run_speed_test: 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 run_speed_test? +

run_speed_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_speed_test? +

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

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

run_speed_test 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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hpe Networking's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.