device_primary_get

Get the user's preferred device for auto-connect. Mobile, web, and the CLI use this when the user has multiple machines registered — single-device users auto-connect regardless.

SERVERYaver SOURCEyaver-cli

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/io-github-kivanccakmak-yaver/device-primary-get.md

WHAT IT DOES

What device_primary_get does on Yaver

AI agents call device_primary_get to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why device_primary_get is rated Low

This tool retrieves configuration data (the user's device preference) without modifying, executing external operations, or causing destructive changes. It is a straightforward Read category tool with minimal security impact — knowing a device preference is informational only and does not enable harmful actions.

From the tool's definition The tool description states 'Get the user's preferred device' — a retrieval operation with no modification or side effects. The verb 'Get' and the context of querying device preferences confirm it is a read-only query.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs device_primary_get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For device_primary_get, this is the rule to start with:

device_primary_get Allowed

device_primary_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "device_primary_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every device_primary_get call is checked against it from then on.

FAQ

Questions about device_primary_get

What does the device_primary_get tool do? +

Get the user's preferred device for auto-connect. Mobile, web, and the CLI use this when the user has multiple machines registered — single-device users auto-connect regardless. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on device_primary_get? +

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

What risk level is device_primary_get? +

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

Can I rate-limit device_primary_get? +

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

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

device_primary_get is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →