getDeviceInfo

Get device model and identification information

Server Lyngdorf MCP Server thejens/lyngdorf-mcp
Category Read
Risk class Low
Parameters 00 required

What getDeviceInfo does on Lyngdorf MCP Server

AI agents call getDeviceInfo to retrieve information from Lyngdorf MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why getDeviceInfo needs a policy

This tool queries and returns static device information (model, identification details) without modifying, executing, or deleting anything. It is a pure read operation with minimal security risk. The other sibling tools like 'getAudioStatus', 'getBalance', 'getSource' etc. are similarly read-only status queries, confirming the pattern.

From the tool's definition Tool name 'getDeviceInfo' and description 'Get device model and identification information' indicate a retrieval operation with no side effects.

Questions about getDeviceInfo

What does the getDeviceInfo tool do? +

Get device model and identification information. It is categorised as a Read tool in the Lyngdorf MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getDeviceInfo? +

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

What risk level is getDeviceInfo? +

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

Can I rate-limit getDeviceInfo? +

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

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

getDeviceInfo is provided by the Lyngdorf MCP Server MCP server (thejens/lyngdorf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.