Gets device ping data by registration key.
AI agents call getdevicepingdata to retrieve information from Revel Digital MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves device health/status information (ping data) by registration key without creating, modifying, deleting, or executing any operations. It is a passive data query with no side effects on the infrastructure or data state. Severity is low because device ping data reveals only operational status metrics, not sensitive credentials or critical control information.
From the tool's definition 'Gets device ping data' indicates data retrieval with no modification. Monitoring/querying device status (ping data) is a read-only operation.
Attacks that exploit this kind of access
Gets device ping data by registration key. It is categorised as a Read tool in the Revel Digital MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Revel Digital MCP Server MCP server in PolicyLayer and add a rule for getdevicepingdata: 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 Revel Digital MCP Server. Nothing to install.
getdevicepingdata 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 getdevicepingdata 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 getdevicepingdata. 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.
getdevicepingdata is provided by the Revel Digital MCP Server MCP server (reveldigital/reveldigital-mcp-server). 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 →