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

get_client_roaming_history

A read tool on the Hpe Networking MCP server.

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/get-client-roaming-history.md

What get_client_roaming_history does on Hpe Networking

AI agents call get_client_roaming_history 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.

Why get_client_roaming_history is rated Low

The 'get_' prefix and 'roaming_history' indicate this tool queries client mobility data without modifying state. No evidence of destructive, write, financial, or code execution capabilities. Minor confidence reduction due to empty description, but context from server purpose (monitoring and operations) and sibling tools confirms read-only classification.

From the tool's definition Tool name 'get_client_roaming_history' indicates retrieval of historical data with no mutation (get_* pattern).

Questions about get_client_roaming_history

What does the get_client_roaming_history tool do? +

get_client_roaming_history is a read tool on the Hpe Networking MCP server. 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 get_client_roaming_history? +

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

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

Can I rate-limit get_client_roaming_history? +

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

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

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