Retrieves all of the service history records for an appliance.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=
AI agents call list_appliances_rentals_servicehistory to retrieve information from Wpm Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation with no side effects. It queries and returns existing service history records for an appliance, which is a classic Read operation. The 'list_' prefix and 'Retrieves' verb confirm read-only functionality.
From the tool's definition Tool name contains 'list_' and description states 'Retrieves all of the service history records'. No modifications, deletions, or side effects are indicated.
Attacks that exploit this kind of access
Retrieves all of the service history records for an appliance.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=. It is categorised as a Read tool in the Wpm Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for list_appliances_rentals_servicehistory: 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 Wpm Mcp Server. Nothing to install.
list_appliances_rentals_servicehistory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_appliances_rentals_servicehistory 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.
Set action: deny in the PolicyLayer policy for list_appliances_rentals_servicehistory. 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.
list_appliances_rentals_servicehistory is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →