get_trusted_device
Get details about a specific trusted device
This record as markdown: /tools/takashito-linode-mcp-server/get-trusted-device.md
What get_trusted_device does on Linode MCP Server
AI agents call get_trusted_device to retrieve information from Linode MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_trusted_device is rated Low
This tool retrieves information about an already-trusted device in the Linode account. It performs a simple read operation without creating, modifying, deleting, or executing any infrastructure changes. While trusted device details could be sensitive (e.g., device identifiers, last login times), the tool itself only reads existing data and does not enable unauthorized actions independently.
From the tool's definition Tool name 'get_trusted_device' and description 'Get details about a specific trusted device' indicate a retrieval operation with no modification or side effects. The verb 'get' is explicitly associated with querying data.
Attacks that exploit this kind of access
The rule that runs get_trusted_device safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_trusted_device, this is the rule to start with:
get_trusted_device is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every get_trusted_device call is checked against it from then on.
Questions about get_trusted_device
Get details about a specific trusted device. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for get_trusted_device: 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 Linode MCP Server. Nothing to install.
get_trusted_device 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 get_trusted_device 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 get_trusted_device. 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.
get_trusted_device is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linode MCP Server, and thousands of servers like it.
This server
Across the catalogue