AI agents call getDevice to retrieve information from Memnote without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves information about a device without altering any data. It is a straightforward query operation with no destructive, financial, or code execution implications. The blast radius of misuse is minimal—an agent could only access existing device information it is already permitted to query.
From the tool's definition Tool name 'getDevice' with description 'Get a device' indicates a retrieval operation with no modification or side effects. Consistent with other Read tools on this server like 'getNote' and 'getTag'.
Attacks that exploit this kind of access
Get a device. It is categorised as a Read tool in the Memnote MCP Server, which means it retrieves data without modifying state.
getDevice accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Memnote MCP server in PolicyLayer and add a rule for getDevice: 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 Memnote. Nothing to install.
getDevice 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 getDevice 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 getDevice. 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.
getDevice is provided by the Memnote MCP server (@randomfact/memnote-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 →